How to work on jira tickets #4

alastair · 2017-03-13T16:32:59Z

Some rough text on how to work on jira tickets. Mostly intended to try and stop the "can I work on this?" comments that we're getting.

Does it make sense to call this Jira.md or does it fall into the wider Bugs.md

Do we also want "how to report bugs", or is that more suited to the wiki?

I wrote the workflow text based on the workflow that we have in AB. I don't know if this is the same in other projects. I seem to recall that they all use the same workflow, so I hope it's ok. If not, please propose prose that better suits what we do/try to do.

Do we want so much text, would a pretty diagram also be useful?

Freso · 2017-03-13T16:37:15Z

Do we also want "how to report bugs", or is that more suited to the wiki?

FWIW, this is already on the wiki: https://wiki.musicbrainz.org/How_to_Report_an_Issue

Freso

LGTM, FWIW.

mwiencek · 2017-03-13T16:53:29Z

Jira.md

+
+### Working on tickets
+
+If you want to work on a ticket, you don't need to ask for permission. Just check


Maybe it'd be good to mention that if something is marked "Decision Required," they should resolve any open questions first. I think this status is specific to our workflow.

mwiencek · 2017-03-13T16:54:44Z

Jira.md

+
+When you finish the task, open a Pull request on the relavent project. See [GitHub.md] with
+additional information about how to name and submit a Pull Request. In Jira, click `Resolve Issue`
+to mark that a review has been submitted, and paste a link to the GitHub pull request URL as


I noticed there are three different capitalizations of "pull request" here. :)

Pull request Pull Request pull request

Also, I assume ticket and bug refer to the same thing. We should settle on one.

I like ticket, because it's broader (task, improvement, etc)

mwiencek · 2017-03-13T16:57:22Z

Jira.md

+`Start Progress`. This shows others that you are actively working on a task.
+
+When you finish the task, open a Pull request on the relavent project. See [GitHub.md] with
+additional information about how to name and submit a Pull Request. In Jira, click `Resolve Issue`


In MBS at least, they have to click "In Code Review." I guess it's different for other projects.

Some projects have the same workflow set on them. Perhaps we should make it a default.

I think the workflow for AB and LB is the same, but I'm not sure about the others. Obviously MBS is different. Can someone provide us with a list of what project has which, and what the steps are? @Freso? I don't know if this is something that can only be seen by an admin or by everyone.

well. at least there's only 2... Do we need to bring this up at a meeting? I note that there are only 2 webapp projects on default. i wonder if they're just on default because no one changed them.

Can you post an image or text description of the MusicBrainz workflow? (from the MBS equivalent of https://tickets.metabrainz.org/plugins/servlet/project-config/AB/workflows).

I donno if this helps/is needed--but I made a diagram to discuss my workflow--I could easily adapt it.

gentlecat · 2017-03-13T17:03:41Z

Do we also want "how to report bugs", or is that more suited to the wiki?

FWIW, this is already on the wiki: https://wiki.musicbrainz.org/How_to_Report_an_Issue

Perhaps this page can be generalised to apply to all projects and maybe even moved there?

Does it make sense to call this Jira.md or does it fall into the wider Bugs.md

Or maybe even Ticket_tracking.md?

gentlecat · 2017-03-13T17:07:21Z

Jira.md

@@ -0,0 +1,29 @@
+# MetaBrainz bug tracking
+
+MetaBrainz uses Jira to track bugs. It is hosted at https://tickets.metabrainz.org/


gentlecat · 2017-03-13T17:08:23Z

Jira.md

+
+MetaBrainz uses Jira to track bugs. It is hosted at https://tickets.metabrainz.org/
+
+Each main MetaBrainz project has its own project in Jira.


Maybe also link to https://tickets.metabrainz.org/secure/BrowseProjects.jspa.

gentlecat · 2017-03-13T17:09:34Z

Jira.md

+
+Each main MetaBrainz project has its own project in Jira.
+
+### Working on tickets


Should this be ## Working on tickets?

gentlecat · 2017-03-13T17:10:56Z

Jira.md

+`Start Progress`. This shows others that you are actively working on a task.
+
+When you finish the task, open a Pull request on the relavent project. See [GitHub.md] with
+additional information about how to name and submit a Pull Request. In Jira, click `Resolve Issue`


Some projects have the same workflow set on them. Perhaps we should make it a default.

gentlecat · 2017-03-13T17:14:06Z

Jira.md

+to mark that a review has been submitted, and paste a link to the GitHub pull request URL as
+a comment.
+
+Once a review has been successfully merged, the project admin will close the ticket.


It would probably more correct to say it like this:

Once a pull request has been reviewed and merged by one of the project maintainers, it can be closed and marked as "Fixed".

gentlecat · 2017-03-13T17:17:10Z

Jira.md

+
+When you finish the task, open a Pull request on the relavent project. See [GitHub.md] with
+additional information about how to name and submit a Pull Request. In Jira, click `Resolve Issue`
+to mark that a review has been submitted, and paste a link to the GitHub pull request URL as


Also, I assume ticket and bug refer to the same thing. We should settle on one.

gentlecat · 2017-03-13T17:21:47Z

Jira.md

+they are still going to complete the work.
+
+If you have any questions about a ticket, add a comment. Project leads will automatically
+get sent an email informing them of your comment, so you don't need to follow it up


Project leads will automatically get sent an email informing them of your comment

Not necessarily. People might not receive an email depending on how their notifications are configured. For example, I don't receive emails about every CB ticket. I do receive email if something happens to tickets that I'm watching or ones that I opened.

My reason for this is that I want to stop people from telling me on IRC "hey I did something, can you look". If this isn't global we should do something else. Perhaps just saying this is good enough?

Saying something like "People who are watching this ticket will automatically..." will be more correct I think.

gentlecat · 2017-03-13T17:22:40Z

Jira.md

+get sent an email informing them of your comment, so you don't need to follow it up
+yourself.
+
+When you have assigned a ticket to yourself, set its status to in progress by clicking


"In progress"?

alastair · 2017-03-21T12:42:20Z

Covered all points except the workflow stuff.
I'm happy to move AB and LB to the musicbrainz workflow, which means that all main webapps would use the same workflow and we can refer to it explicitly in this doc.

gentlecat · 2017-03-21T12:46:05Z

Do we keep it Jira.md?

This is a continuation of discussion on #4: #4 (comment).

alastair · 2017-03-21T13:30:58Z

I thought about that - if we consider that contributing guidelines are for people who want to help develop our apps then jira is the tool that they need to interact with for this task. I don't mind keeping it jira.

gentlecat · 2017-03-21T13:50:53Z

Alright.

How to work on jira tickets

fd90068

alastair requested review from gentlecat and mwiencek March 13, 2017 16:32

Freso approved these changes Mar 13, 2017

View reviewed changes

mwiencek reviewed Mar 13, 2017

View reviewed changes

gentlecat reviewed Mar 13, 2017

View reviewed changes

gentlecat self-requested a review March 13, 2017 21:02

Fuschia

e2b9b6e

gentlecat approved these changes Mar 21, 2017

View reviewed changes

gentlecat merged commit 96526bd into master Mar 21, 2017

gentlecat added a commit that referenced this pull request Mar 21, 2017

Rename Jira.md to Issue_tracking.md

fec9133

This is a continuation of discussion on #4: #4 (comment).

gentlecat mentioned this pull request Mar 21, 2017

Rename Jira.md to Issue_tracking.md #6

Closed

alastair deleted the jira branch March 21, 2017 13:46


		### Working on tickets

		If you want to work on a ticket, you don't need to ask for permission. Just check

		@@ -0,0 +1,29 @@
		# MetaBrainz bug tracking

		MetaBrainz uses Jira to track bugs. It is hosted at https://tickets.metabrainz.org/


		MetaBrainz uses Jira to track bugs. It is hosted at https://tickets.metabrainz.org/

		Each main MetaBrainz project has its own project in Jira.

How to work on jira tickets #4

How to work on jira tickets #4

Uh oh!

Conversation

alastair commented Mar 13, 2017

Uh oh!

Freso commented Mar 13, 2017

Uh oh!

Freso left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

gentlecat commented Mar 13, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

alastair commented Mar 21, 2017

Uh oh!

gentlecat commented Mar 21, 2017

Uh oh!

alastair commented Mar 21, 2017

Uh oh!

gentlecat commented Mar 21, 2017

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

gentlecat commented Mar 13, 2017 •

edited

Loading