Hide item statuses for members of a user group

[Matt Perdeck]

In my company, various people can add Jira items to the backlog - devs create bug issues, the PO creates new feature issues, support personnel create suggestions, etc.

The product owner then has to go through a series of steps to get approval for each item before it can be worked on. To track this, I want to give Jira items approval specific statuses - "created", "approved", "rejected", "ready for development", and about half a dozen more.

But then when developers finally work on an item, they need their own statuses, such as "In Progress", "Ready for testing", "Closed", "Cancelled".

I don't want to bother the developers with all the approval specific statuses. That is, I want them to just see the development specific statuses, so when they want to set an item to "Closed", they don't have to wade through all the approvement specific statuses.

Is there a way I can hide certain statuses for certain groups of users (such as hiding the approval statuses from the developers)? It's ok for them to see all the details in the item, I just want to only show statuses to the devs that are relevant to them.

[Vasiliy Zverev]

You could use issue sequrity levels for it. Create at first 2 level - PO and Developers. When issue is on PO side - it is on PO sequrity level. When development starts - set level to Development.

[Deleted user]

Hi @Matt Perdeck,

I assume all the statuses are within one workflow? 

If you are using JIRA Software I would suggest setting up two boards; one for the PO and one for the dev team. 

The first board can have all the statuses that pertain to the PO mapped to each column.

Example of the board columns below for the PO:

Created | Rejected | Approved

The second board can have all the statuses that pertain to the dev team mapped to each column. I assume the dev team are only interested in the Approved statuses and that is where they want to start on issues.  

Example of the board columns below for the dev team:

Approved | In Progress | Ready for Testing | Closed | Cancelled

As as as I am aware you would not be able to hide the status of an issue from a certain user if they have the Browse Projects permission. I think splitting up the workflow between 2 boards that are relevant to each team would be a good focal point for each interested party.

Hope this helps.