You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
I am currently struggling with the value of the status field. In a standard Jira ticket, the status workflow is much more prominent, with the idea being you transition your ticket through the workflow. With it just being a field on the right, it loses its value.
Is this an intended positioning? if so, what's the logic or value of putting status where it is as opposed to where the archive action is?
I personally would like to see the status operate as it does in the rest of Jira.
We leverage Jira Product Discovery for undefined/funnel/backlog ideas, with a focus on definition, socialization, and feedback. Once something is defined and ready to build, that work is managed elsewhere, and linked back to the JPD ticket.
Consequently, I find status extremely useful.
The whole idea of status field in JIRA is to transition from one to other and vice versa In agile process there is continuous delivery and integration if the increment doesn't pass the functional, Automation, Integration, sanity test & merge it moves back for the fix thats why the status field is kept to transition