I have a workflow which uses KanBan BLOCKED states for my team. However I do not want the end users to be able to see the blocked states (they should just show as IN PROGRESS or something.
Is this possible? I do not see an easy way to hide a STATUS state from a group of users however I am able to control which groups can enter into these states by using the CONDITION section of the workflow transition.
No. Visibility of an issue is controlled at the issue level.
It's also quite a bad idea to do this. Let's say I'm one of your end users. I created issue XYZ-123, so I check on it every now and then. One day, it's gone. Why? Why have you deleted my issue? What's wrong? Why are you ignoring my issues? No explanation? Best case, I'm going to be wasting your time asking what's happened. Worst case, I get annoyed at you and leave.
Thanks for the quick reply. I think you misunderstood the question however. I don't want the issue to be hidden. I want certain STATES to be hidden in the issue.
For example a customer files a ticket and it is OPEN. Internally we find that the ticket is blocked on some dependency so we move it to a state called BLOCKED. I wanted to know if the customer view could show the state as IN PROGRSS or simply OPEN and not show the state of BLOCKED. The visibility of the issue itself does not change.
I suspect the answer is no and I may just need to be clever with my naming of the blocked state.
Ok, that does explain it better for me, thanks. The answer is "no but yes". Logically, it's a very bad idea to lie about the status of an issue, so JIRA doesn't support that at all. The status shown *is* the status. But, it is often very useful to group status together, or even hide the complexity and detail from certain types of user. Not quite the same as misrepresenting the actual status, but: If you have the Agile addon, you can do a form of meta-status on boards. The defaults for them tend to set columns To-do, in-progress and done, with those columns often containing more that one status. They don't hide the status, but they do group it up. But I think you want something more like "Service Desk". You've got a JIRA workflow which works for your developers, it's got many status and tells the truth about the issue. But your *customer* only cares about a broader meta-status - the issue has not been seen by you yet (new), it's with you (open, in progress, blocked, on hold, in test, etc), you've sent it back to them for review or more information (with customer), and it's been settled.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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