An easy way for QA testers to indicate successful completion of testing a fix, using the Tested button to go through workflow from Resolved to Verified. Any branch statuses are set to merge, for example 11 status and 10 status flags indicate a need for a merge to the 11 branch or the 10 branch successfully. Branch managers close the JIRA when all merges are completed.
We have a way to set the branch status flag to tested, indicating the fix was tested directly in the branch, after merge.
Workflow from Awaiting Review -> Opened -> Resolved -> Verified -> Closed.
Easy way for a developer or QA tester to be assigned a JIRA indicating work in progress.
A way to bulk change just about any field or workflow in JIRA .
Date indicating when the JIRA was created and when it was last updated.
Easy commenting mechanism.
Field for Test Plan.
Extensive use of labels that are usable by anyone. Used flexibly.
JQL searching mechanism. Easy to search and order by tool, status, reporter, assignee, and so forth.
Indicating the type of issue, bug or feature.
Easy connection to actual code changes.
Prioritization field.
Affected Version(s)
Fixed Version(s)
Easy addition of screenshots and other attachments.
History showing the change in status of the JIRA over time.
Be able to re-open an issue which is not actually fixed.
Connection with Confluence - two way. Able to easily link one or more JIRA issues, including by JQL search queries. JIRA shows connected Confluence pages. Great for README and rellease notes.
Exporting of issues to Excel.
API's available to query and pull data from external languages like Python.
Ability to close issues other than just being fixed, for example Non-issues, Duplicates, Won't Fix (insufficient resources, etc), Incorporated, Incomplete, Can't Reproduce, etc.
Connection between JIRA to show relationships like dependencies, incorporation, duplication, etc. Allows for many-to-many relationship.
Ability to define issues as Security issues, which makes them inaccessible except for those with appropriate permissions.
Group management to control to whom issues can be assigned, use of the QA Tested button, etc.
Allow watching of issues. And automatic set to watcher for issues on which you make comments.