The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Workflow allowing cloning but not editing

JD
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 13, 2020

Hello Jira experts,

To prevent users to edit issue(s) test already executed, I've been asked to create a workflow allowing cloning but not editing of these issues test.

As I'm new to Jira, I've done some digging on Atlassian doc and a lot of tests/mistakes but eventually I created my workflow. Let me be clear, it's working but is not entirely satisfying mostly because of "the cloning part". I've added 2 transitions, "Lock" and "Unlock Edition" managed by an admin allowing user to edit or not the issue..... BUT you can't clone it when the issue is locked. Is there any way to do it ? Because of course I'd like for users to be able to clone a locked issue. 

Here's what I've done :

- 2 steps, "Open" and "Test"

- 2 transitions "Lock" and "Unlock Edition". and here's my Step Properties :

          - (Property Key) jira.permission.create.group       (Property Value) admin

          - jira.permission.create.user                                  denied

          - jira.permission.edit.group                                   admin

          - jira.permission.edit.user                                      denied

 

Not sure I've been clear, English is not my first language so please, feel free to contact me if you need any additional further information.

 

 

0 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.