Skip to main content

Jira Ticket Statuses

Updated
  1. Open – ticket has not been worked on and is not currently prioritized.  These items are in the large backlog  
  2. Next Up –It has clear acceptance criteria, is assigned or ready to be assigned and can be moved to Ready for Development.  
  3. Ready for Dev– this item is now in the engineer’s priority list.  
  4. In Dev – Developer has started work. 
  5. Waiting – Work is paused.  Waiting for more information, a decision, feedback from customer, etc. 
  6. Code Review – the engineer has completed their code and is having a peer complete a code review  
  7. Ready for QA – this item is ready for quality assurance testing. 
  8. In QA – Quality Assurance Team is testing  
  9. Ready for Release – work is complete and tested.  Will release upon the next full deploy to production. Jira items that do NOT need QA testing can be moved directly to Ready for Release if they have passed Code Review and developer deems no additional testing is needed.   
  10. Scheduled for Release – Status is used for the Chambermaster (CM), Mobile Apps, (SAPP) and GZCMS (WP) items that will be released in a batch and/or on the regular bimonthly schedule.  
  11. On Production – Status is used for the Chambermaster (CM), Mobile Apps, (SAPP) and GZCMS (WP) projects. The code is now out on production and ready to be checked. In the case of mobile apps, this means the changes are approved by Google or Apple and the new version is available in the store. QA will then verify the item in the production version of the app. 
    1. On Production field  (not status)– is used for the GZ project and indicates it went to production and still needs to be tested/approved by QA or some other further action is needed before it can be closed.
  12. Closed  – this task is considered completely done (if there’s code, it’s on production) and no further work will occur on it unless it is reopened.  Often a new task is created rather than reopening an existing task, whichever option seems to make the most sense for the particular case.  
    1. Resolution field on a Closed issue is one of the following: 
      1. Delivered - Work is live on production.  
      2. Done – Sub-task that is done and merged to the branch, but not on production, or non-development work that is complete 
      3. Duplicate – Jira issue was a duplicate of another Jira issue 
      4. Cannot Reproduce - All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. Developer will add additional logging if it is possible and practical.  If more information is reported by the customer, please reopen the issue. 
      5. Won’t Do – This issue won’t be actioned. Product may have determined the change does not fit with our overall goals or there is not enough benefit for the cost to implement.

 

What happens in Happy Fox when a Jira ticket is closed:

  1. Jira issue status field will be set to Closed 
  2. Happy Fox ticket will be set to In Review 
  3. The Support Notes from the Jira issue will appear as a private comment on the Happy Fox ticket.   
  4. The assignee on the Happy Fox ticket will get a notification.