This question is in reference to Atlassian Documentation: Defining status field values
I am curious if status category actually has any role aside from it's logical role.
In the documentation, it mentions about being relevant to where it is placed in a board column. I haven't encountered it to be so. You can place any status with any status category in any column.
Thank you Jobin. I will accept that answer.
I just find the definition misleading. It doesn't really help in identifying where issues are in their lifecycle (since it can be placed anywhere). Nor is it relevant to map status to columns in boards (since it can also be placed anywhere).
Category — choose a category that this status will be grouped into: 'To Do' (blue), 'In Progress' (yellow) or 'Done' (green). Categories help you identify where issues are in their lifecycle, particularly in places where a large number of issues are rolled up, e.g. Version Details page, Sprint Health Gadget. The category is also used to map statuses to columns in JIRA Software , when creating a new board for an existing project.
What exactly controls whether an issue gets a line through it's ID (strikethrough)? Does that only happen when an issue reaches the right-most column in a board?
And if that issue proceeded with additional workflow statuses beyond those on that board (e.g. release management), would it remain struck-through?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs