Hello,
I hope everyone is doing fine. I have created new issue type by the name of "Story Bug" and it is sub-task level issue. The idea behind is that within the story I'll be able to see the bugs reported. This works perfectly for story and the sub-tasks shown within that story.
If instead of story, user created a task and sub-tasks below and want to create a bug as well. I'll create a new issue type by name of "task bug" but I want that issue type to show only when user selects tasks.
I want story bug to show only when story is selected and task bug when task is selected. In the picture above, the parent type is Story and Story Bug is created. When User selects task instead of Story I want to show the Task Bug instead of Story Bug.
I hope I have made my question clear.
If your deployment type is CLOUD indeed, then I'm sorry to be the bearer of bad news, but you can't do that. If you were on Jira Server, you could easily do that with Scriptrunner's behaviours.
What you can do in your case is to add a validator in each subtask's workflow. This validator will check the parent's issue type:
Hope that helps.
Alex
@Alex Koxaras -Relational- - Thank you so much for your reply. Yes, I am using Jira Cloud. Why there are so much limitations on Jira Cloud. Jira is used worldwide and yet there are so many restrictions in Jira which is so irritating.
I am using the same workflow for all the issue types currently. I'll need to create separate workflows for each issue type for this to work?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Hizkeel Khan in Jira cloud you are working with REST api, where in the server edition you are working with Java api. In addition, there are a lot limitations for security reasons.
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.