When I create an issue within/sitting in my custom issutype, the issuetype is of the same type as my custom issuetype, but I want it to be of issuetype Bug. Do I spescify this in my custom workflow steps? Because there I can see that my 'Create my issutype. uses the default screen, and it is also the screen showing up as I want, but it is of the same type as the same custom issuetype I am sitting in when creating a new issue (using my own statuses and transistsions).
Um, I'm a little confused about "create an issue within" my issue type.
Do you mean subtasks? Where are you doing this creation?
For what it's worth, think of the issue types as a simple list in two sections. One section is "parent" issue types, and another is "subtask" issue types. All issue types must be unique across the list, and you can use "issue type schemes" to define sub-sets for projects (e.g. have 50 issue types, but project A only uses 3)
We've mentioned this before, and it's worth saying again - the selection of an issue type is done BEFORE the workflow even begins. Because the issue type is a hook to hang the workflow on (e.g. you've got bug-workflow for handling bugs and sub-bugs, and issue-workflow for issues). You need to stop thinking of the workflow as having anything to do with the creation of issues - it only starts to have an effect after you have started to create the issue and know the issue type.
What I ment with "within an issuetype" is that I am standing in my custom workflow that is made for the custom issuetype, say issuetype A, and I have some steps that my issuetype A goes through. However in one of these steps I want to stop up and say lets create a new issuetype in this step (of type bug/default Jira) of the workflow using the default screen. This actually which works at the moment, it shows the default screen, not the custom screen that I have defined for i.e. create the issue of my custom type, but the problem is that the issuetype is of A not Bug, even though I have used the default screen as transistion screen when defining the workflow.
I hope I managed to expalin this so you understand.
Ok, so, to repeat this back to make sure I have understood...
You want to create an issue as you progress through the workflow of an existing issue. For example, if you click "move to testing" on ABC-123, then ABC-155 gets created.
How are you doing that at the moment? There is no mechanism for it in Jira at all, so I don't know what you've set up, unless you've got some plugin that tries to do it. If that's the case, then what is the plugin?
Mmm, well, that's not going to happen, there's simply no structure there to allow it.
The best you can do is to have a transition screen that prompts the user for information, and a post-function or listener that scans the information and creates your new issue separately from the current issue, when the user commits their change.
Or, you coul dput something on the screen that the user clicks, and it pops a second Jira window with the "create issue" screen pre-populated for them, but that will still leave the original issue sitting there waiting for them to commit the transition (which they don't actually have to do)
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs