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!
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.
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.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG