We used to use sub-tasks but have decided against using them anymore. I moved about 5,000 sub-tasks to one sub-task named simply "sub-task". The reason why is because you cannot bulk change a sub-task to be an issue. So I am stuck with one "sub-task" within my issue type scheme. My question is this: is there a way to allow sub-tasks (I don't want to manually move them to be issues) but prevent users from creating new ones? I have about 300 users and they are very difficult to train. Thanks!
In the sub-task workflow in the Create Issue transition put a custom script validator (using Script Runner plugin):
import com.opensymphony.workflow.InvalidInputException invalidInputException = new InvalidInputException("Subtasks cannot be created manually.")
Problem is that it will complain after user pressing 'Create' button, not before.
There are some great suggestions from the user community around moving those sub tasks into issues: https://answers.atlassian.com/questions/37825
If you can get this working then you can just disable sub-tasks natively.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I should say I am looking for something within the workflow that would prevent users from creating sub-taaks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Suzanne,
You can remove any subtask issue types from your issue type configuration scheme.
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.