Bug Tracker: Difference between revisions
Silentbird (talk | contribs) (update URLs) |
Silentbird (talk | contribs) (Edit language and remove part on anonymous reporting (now disabled due to spam)) |
||
Line 1: | Line 1: | ||
<small>[[Development]] > Bug Tracker</small> |
<small>[[Development]] > Bug Tracker</small> |
||
JIRA (https://tickets.metabrainz.org/) is the platform used by the development team and members of the community to track bugs and development progress on the [[MusicBrainz Server]] source code. |
|||
== Reporting bugs == |
== Reporting bugs == |
||
:''Want to report a bug? [https://tickets.metabrainz.org/secure/CreateIssue!default.jspa Report it here!] |
:''Want to report a bug? [https://tickets.metabrainz.org/secure/CreateIssue!default.jspa Report it here!]'' |
||
⚫ | To report a bug or unwanted behavior in the server code, [https://tickets.metabrainz.org/secure/Signup!default.jspa create an account] and report it under your name. With an account, you can discuss with other users using comments if more feedback is needed and receive email updates about the bug(s) you've submitted or any other bugs you're interested in keeping tabs on. |
||
If you find a bug or unwanted behavior in the server code and want to report it you have two options. |
|||
⚫ | <!-- If you do choose to anonymously report a bug, keep in mind that commenting anonymously has been disabled. So in order for you to leave additional information or answer a developers question you will need to either have created an account or manually follow the issue's progress and use the guest account to comment when necessary. The guest account has both username and password set to <code>musicbrainz</code>. |
||
⚫ | |||
⚫ | |||
⚫ | If you do choose to anonymously report a bug, keep in mind that commenting anonymously has been disabled. So in order for you to leave additional information or answer a developers question you will need to either have created an account or manually follow the issue's progress and use the guest account to comment when necessary. The guest account has both username and password set to <code>musicbrainz</code>. |
||
⚫ | |||
== Workflows == |
== Workflows == |
||
Line 20: | Line 17: | ||
=== "Decision required" status === |
=== "Decision required" status === |
||
The "decision required" status is |
The "decision required" status is used when an issue or task requires a decision to be made before developers can move on and start/continue their work. |
||
The procedure to follow is: |
The procedure to follow is: |
||
# Post a comment that clearly states what needs |
# Post a comment that clearly states what needs to be decided. |
||
# Change the status to "decision required" and assign the issue to the person |
# Change the status to "decision required" and assign the issue to the person expected to make the decision. |
||
# When a "decision required" issue is assigned to you, first determine if it's your decision to make. If not, find the right person and re-assign the issue to them. |
# When a "decision required" issue is assigned to you, first determine if it's your decision to make. If not, find the right person and re-assign the issue to them. |
||
# When an issue is your issue to decide and when you've made your decision, note the decision in a comment. |
# When an issue is your issue to decide and when you've made your decision, note the decision in a comment. |
Revision as of 11:21, 8 January 2019
Development > Bug Tracker
JIRA (https://tickets.metabrainz.org/) is the platform used by the development team and members of the community to track bugs and development progress on the MusicBrainz Server source code.
Reporting bugs
- Want to report a bug? Report it here!
To report a bug or unwanted behavior in the server code, create an account and report it under your name. With an account, you can discuss with other users using comments if more feedback is needed and receive email updates about the bug(s) you've submitted or any other bugs you're interested in keeping tabs on.
Workflows
The following are JIRA workflow conventions that the development team uses.
"Decision required" status
The "decision required" status is used when an issue or task requires a decision to be made before developers can move on and start/continue their work.
The procedure to follow is:
- Post a comment that clearly states what needs to be decided.
- Change the status to "decision required" and assign the issue to the person expected to make the decision.
- When a "decision required" issue is assigned to you, first determine if it's your decision to make. If not, find the right person and re-assign the issue to them.
- When an issue is your issue to decide and when you've made your decision, note the decision in a comment.
- Change the status back to open and assign it to the person who should continue to work on the issue (unless in the course of the decision making the task has been passed to someone else).