doubt on workflows permissions

Hi there,

We have a doubt on workflow permissions. We would like that some status in a given workflow are invisible to some people, but I think this is not possible, so we thought of two solutions that, as far as I have read, are not possible either:

1) Create a subtask at a given status, which will have a different workflow. Problem with this is that sub-tasks inherit parents permissions, so this people would be able to see it anyway.

2) Create a different issue type in the same way as subtasks in 1), but in this case we would need this issue to be created automatically when the 'parent' issue gets to the given status and to transitionate the 'parent' issue to the next status when the 'child' issue is closed. Is this possible?

Can you help us, please?

4 answers

hi,

Can you explain your requirement in detail?

With the custom post function you can set the security of subtask to different from the parent.

When you transition in the status where only some people should be allowed to see the issue set via postfunction a new security level (for only those people ). When you leave that status set the security level back.

I'm not sure what are you trying to achieve, but I think it's totally the opposite of the JIRA best function, a real time reporting to the client. If you change the security level in the post-function then the use who can't see it anymore will think it has been erased for example.

To find a solution we need to know first what you really need.

Hi,

you can define 2 security levels in your project: default and restricted. In the default everyone involved in the project can see the issue, while in the restricted some people can't.

In the incoming transitions to the workflow status, you can add a postfuncion that changes the security level from deafult to restricted; and the outcoming transitions, change it back to default.

I think you should explain more your requirements, because this way, some users can't see the hidden issues until they leave the "hidden status". Then, the users will see the issue and their full history again (including when thy're hidden) ... so ... this may not make sense in your environment

...

HTH

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,315 views 14 20
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot