Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,296
Community Members
 
Community Events
176
Community Groups

The value of the status field?

Hello All

 

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. 

3 answers

1 vote
Rohan Swami Atlassian Team Dec 02, 2022

Hi @Ben Arundel , as others have said there's less of an emphasis on moving items through a workflow in Jira Product Discovery as there is in Jira Software.

Thanks for your feedback!

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

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events