...
For tickets for which there is enough information, three four outcomes are possible. For any ticket that duplicates another already in JIRA, a comment is added with a reference to the ticket it duplicates, the status is changed to Closed-Duplicate, and the ticket exits the workflow. For any ticket that the sub-team determines we will not do, the status is changed to Closed-Will Not Do and the ticket exits the workflow. For any ticket most tickets that the sub-team assigns a priority, the status is changed to Ready for Implementation and the ticket moves on. . Occasionally tickets that a deemed a good idea but that have a very narrow use case or are considered good starter issues for community contribution may be changed to a status of Ready for Community Developer.
Next, as resources permit, the Program Team assigns the ticket to a particular sprint cycle, software version, or developer. The status is changed to Developer Assigned.
...