Now there are 4 issue types as follow.
Only C sub-task can be created for A issue type, and only D sub-task can be created for B issue type.
through use of web-items , you can achieve this feature objective.
By web-item , you can have button to create specific subtask for the issuetype (create issue action).
I think that you can use the JIRA Behaviours plugin to achieve that as it allows adding custom validation (both client side and server side) when creating an issue. So you can implement validator that checks if the selected subtask is valid for the issue type that is being used as sub-task parent. I can't give a sample code as I'm not very familliar with the Behaviours plugin but if you take a look here - https://jamieechlin.atlassian.net/wiki/display/JBHV/JIRA+Behaviours+Plugin it should be easy to implement such logic
Hello Community, Today we are going to talk about the three Scrum Roles. There is the Development Team, the Scrum Master and the Product Owner. In my opinion these three are all really impo...
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