How do I hide issue workflow status from a user group?

[João Monteiro]

Hi,

Our team uses Jira for software development with a simple kanban workflow "to do", "in progress", "qa" and "done". We want to add our client to our project in a specific board so they have access to all the information about the issues in the backlog and in the sprint. 

We don't want our client to know the progress of the issue during the sprint. To achieve that, we need to hide the issue status from the issue for a specific group of users.

Has anyone experienced this? I thought it would be an easy problem to solve in JIRA but i'm finding no solution. 

Thank you,

João Monteiro

[Martin Bayer _MoroSystems_ s_r_o__]

Hi @João Monteiro I'm sorry but it is not possible.

[João Monteiro]

Hi @Martin Bayer _MoroSystems_ s_r_o__ , thank you! isn't there an ingenious workaround on this? Such as having the client see one board and that set of issues are automatically cloned to an internal board that has the workflow status? 

[Nic Brough -Adaptavist-]

You could drop the status off boards, but your screenshot is of the issue navigator, which will always tell you about the status (and other fields) for the issues you've chosen to see in it.

You could set issue security so that people can't see the entire issue, but that's going to be very counter-intuitive for your clients - their tracked issues will disappear.

Jira Service Management does actually do something like this though - if your clients only used requests instead of having full access to your Jira as "developers", then you don't have to expose your internal workflow to them at all.

[João Monteiro]

Thank you @Nic Brough -Adaptavist- ! Yes, I thought of having the issue disappear from the user when it transitions from "todo". As you said, it's ver counterintuitive, we like to have the issues open for the client to connect with. 

I thought of the following: 

Would it be possible to have a board (for the client) that when an issue is created there, another (cloned) issue is created in our internal board that when the "mother" issue is edited, the internal issue is also edited?

That way we would have an internal issue linked to an issue for client visibility.

Thank you so much!

[Nic Brough -Adaptavist-]

You could do that, but you might find it quite clumsy, you'd have to think a lot about what updates flow between the two issues (I'd be tempted to keep it simple and do it by project rather than hidden issues - you can hide the whole project from your clients)