restrict "move" operation for sub-task

[David Plesu]

Hello,

I hope this message finds you well!

I have a question about changing the parent of a sub-task.

In my instance some users change the parent of the sub-task, and is not a story, is a epic.

And this is not the correct approach.

Is there a possibility to restrict this?

Thanks in advance!

Best regards,

David.

[Kristian Walker _Adaptavist_ · Accepted solution]

Hi David,

Thank you for the update.

I can confirm it is not possible to restrict the Move options shown above as Jira does not allow this.

The only thing you can do is to stop users from seeing this move option by editing the Move Issues permission in the projects permisison scheme to not allow users permisison to move issues.

I hope this information helps.

Regards,

Kristian

[David Plesu]

Hi @Kristian Walker _Adaptavist_ ,

For me is good enough.

Thank you!

Regards,

David.

[Kristian Walker _Adaptavist_]

Hi David,

I am glad this answer helped :)

Regards,

Kristian

[Asha Goyal]

Hi @David Plesu 

Kindly refer this link to restrict issue type.

https://www.adaptavist.com/blog/restricting-issue-types-with-scriptrunner-for-jira

Hope it helps 

Thanks

[David Plesu]

Hello,

Thank you for the quick response.

I don't think I was clear enough.

Let me explain one more time:

I have a sub-task, that is under a user story, which is good!

Now a user go in the actions of the sub-task, and are clicking "Move"

 Now they select "Change the parent" - this operation is correct, and they should select a new user story.

Instead they select a epic, and this is working here. And automatically the sub-task parent is the epic. And the user story is missing.

Thank you.

Best regards,

David.

[Kristian Walker _Adaptavist_]

Hi David,

I can confirm with ScriptRunner that for Jira Cloud it is possible to restrict issue types only on the Create screen currently with Behaviours, and the example here shows how to do this.

Also, this documentation shows what fields behaviours support on the Create Screen and what fields it supports on the issue screen.

An alternative approach would be to use a Script Listener and to check when the issue type changed in the script and if the issue had subtasks and if it did to change it back to its correct value and add a comment saying it was changed back.

I hope this information helps.

Regards,

Kristian