I am also looking at this type of issue from the perspective of support verses development. Their workflows are different and the support workflow needs to feed into development workflow but without exposing the development workflow. I was thinking that I could create a new issue type for support to use that can be assigned to only support users. When the support is ready to turn over the issue to development, they can change the issue type. I have not yet figured out if we can restrict users to certain issue types or not. I would attempt to make the development open state available to the support group, but then disallow access or read-only access to the development workflow for the remaining states. When the issue is resolved by development, they would change the issue type back into the support issue type.
good idea, I wonder how to do that too, as well as make some users not have access to certain parts of my project, if a user sign up from E-mail / Jira account , that user has complete access to my project, which is not the idea, just want them to be able to see part of it (Issue ticket) that I shared with them and able to comment it, but nothing else.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events