Hey guys,
I am working in Jira Service Desk on some issues of type 'incident'. In the 'More' section in the form, by default I see two options 'Create sub-task' and 'Convert to sub-task'. Is there a way for me to remove them only for that specific issue type (so that they do not show for Incident, but they do show for Change for example). Has anyone done this already?
Thanks!
Community moderators have prevented the ability to post new answers.
We can do this using Adaptavist ScriptRunner plugin to block creation of subtasks based on issuetype.
Create a separate workflow for subtasks in your project. Add a 'simple scripted validator' on the subtask issue workflow create transition to block creation of subtasks for particular parent issue types.
For example;
issue.getParentObject().getIssueTypeObject().getName() != 'Incident'
Will block creation of subtasks for all parent issue types of 'Incident'
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm going to necro this thread to note that the above suggestion works great for preventing users from using More > Create Sub-Task. However, it does not prevent users from using More > Convert to Sub-Task, even if the target parent issue is of an issue type that you've excluded using the scripted validator.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There's no way to remove the option without doing some coding, but @Ojase has given you a really good way to stop the users doing the wrong thing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You will need to write a new app for Jira, one that can hide options from the users.
I would question why you want to do this though. Why can't you trust your users not to convert items when they shouldn't?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thank you for answering @Nic Brough -Adaptavist-
converting sub task process allows all issue Types to be parent of sub task i.e. epic and bug, i thought using hide UI elements concerning convert to sub-task + adding a script handling cases of which it can be achieved i.e. parent can be only task etc' else to stop convert process
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But why? Why are you trying to stop your people doing this?
What is broken in your processes that they think they want to do the wrong thing?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.