On the right side of the screen, the Bug Status and such information is getting displayed. It would be nice if we could loop over attachments in Bugzilla and display the attachment name as a link to the Bugzilla attachment. This would be especially nice for auto generated bugs.

It's not clear if they are there before the comment or just get overwritten after the comment is made.

It would be nice to be able to re-open a bug in Bugzilla when I comment in Git Hub

The two should match. In a perfect world updating Bugzilla Summary would update GitHub Title and visa versa. Not a huge priority, but something that would be nice.

Also of note, when you update the GitHub title the bugzilla link breaks (no longer a link).

Looks like a recent GitHub update has removed github/jquery from the dependencies, meaning our code breaks. Going to have to dig into this, but my main concern is capturing PJAX events.

Currently I have to got to pull requests, then milestones to get these buttons. I'd like to have a button on the pull request so I can pull up in Bugzilla all of the related bugs for this Milestone. Since the Milestone can be edited in the Pull Request I'm not entirely sure how easy this will be.

Labels sync when editing on an existing pull request, but when adding a pull request with labels predefined, the bug is not getting updated.

Should make it so when the pull request is created, the labels are synced. May be easiest to do this as part of the code that syncs the pull request link field.

Add a new field to Buzilla called Labels. When we push comments to Bugzilla we also should push the Labels as a comma delimited list. Sure Labels kind of match up with Status in Bugzilla, but there are 'statuses' we are missing, such as Help Needed, and WIP the list goes on....

Currently when I make a release there is an option to close the bugs in Bugzilla. However, I don't want to close the bug UNTIL the release is in production. Therefore the close bugs in Bugzilla option should always be available as an option.

Line comments aren't getting sent to Bugzilla when doing a review. Need to figure out how to send them when the review is submitted.

Bugzilla Milestones should show up in GitHub as options under Milestone.

Why can't we pull the Milestone from the bugzilla bug into GitHub? Else, can query bugzilla for available milestones based upon the github repository? It is starting to sound like we may need a mapping API between the two more and more.

When viewing a Pull Request, the first tab is Conversation and boy does that look great. Now click on Commits. We lost our link to Bugzilla at the top (I think this is a bug, if I come in from Files Changed the link works). Can we pull comments from Bugzilla and inject them in here? Do we want to? Files Changed, looks pretty good but can we add any additional knowledge here?

One thing I'd love to do is pull in requirements from Bugzilla and map them code in GitHub. I don't have a good strategy yet but this is something I'd love to brainstorm.

Received the following warning when installing the latest version (happens during a reload as well as during initial installation):

There were warnings when trying to install this extension: Unrecognized manifest key 'applications'.

Despite the warning everything seems to be working ok, so maybe this is a low priority item.

I can take this on in a couple of weeks when I have time if @jtl3d doesn't get to it first.

In CWOT, I use the format "bug-95484" for my branch names. Adding the bracketed bug number to the pull request title seems redundant in that case. I suggest we use the branch name as an alternative hint for the bug association.

Last couple times I've done a review comment, the filenames and line numbers have not been transferred in the BZ comments. See [96935] for an example.

• do something else
• do something
• finalize
• submit

Upon creating a release in Git Hub it would be nice to change the code status to 'In Staging' in Bugzilla for any bugs listed in the comments.

I've been listing the pull requests in the release comments with title, so the bug # will be in the title as well, or gives you the option to change them en-mass.

Could we send attachments attached to PR comments to the bug in Bugzilla?

When closing a milestone in GH, it would be cool to have a prompt ask if you want to close the bugs in that milestone in Bugzilla.

We could implement this in numerous places, but basically where I'd like to implement this is when I create a release, I'd like the option to update all the bugs in the release to use a new QA contact in Bugzilla. However, this is probably something we will want in the pull request as an option too.

To open this up to the world, we need to remove some hard-coded things and make it more configurable.

@sjmatta can hopefully knock this out quickly.

I want to add a gradle build file so that we can build the .zip archive needed to upload to the web store.

Everything except these files would be added to the archive:

• .gitignore
• README.md
• images/store
• All the gradle stuff

Would want to add the resulting .zip to the .gitignore file, probably.

Firefox's WebExtension API should mean the plugin will just work in FF. I tried it, and it does partially work, but any call to Bugzilla is tripping a cross domain policy error. I don't know why, I've tried adding the appropriate permissions, but in Chrome the content-scripts run in their own CSP so you can do XSS just fine... maybe a future update will work, or maybe we should move the calls from the content-script to the background page? Either way, it's so close to working in FF!

I would like to be able to update the Planned Delivery Date for all bugs listed in a release. This way I can say, 'we plan to deliver this feature in the next release'.

Tried doing a few actions and the plugin asked me to login multiple times at the top. ( I did not see it originally)

This issue is that it should only display once even if I try multiple actions without loggin in or at the very least give me a way to remove the other login requests without having to refresh the page.

I use a lot of github internal linking to other pull requests especially to and from epics. In error when I added time to my bug it was added to the epic. Here is how the reproduction script.

1. Navigatted to this pull request https://github.com/ditinc/ia-scap/pull/196
2. Once it loaded I saw the quark was correct in the extra data we inject.
3. Then I clicked the link to pull request 234 which is three lines from the bottom in the first comment.
4. Looking at the extra information we inject the quark has not changed correctly and is still looking at the epic
5. Add time to this quark
6. Navigate to the epic in quantum
   • you will see the time you just added was added to the epic not the quark.

At least for the Review form, if you enter .1 as the hours worked and click submit, you'll get a comment in Bugzilla created even though HTML5 form validation prevents the review from being submitted in GitHub.

I just noticed this yesterday, and it's been happening every time I open a pull request and switch the base branch. As soon as you change the base branch to something other than master, the Create pull request button becomes disabled. It's only until you refresh the page that it becomes enabled again.

P.S. The Submit new issue button had the same problem when I clicked to create an Issue. It became enabled when I refreshed the page.