Default issue type when creating story within heirarchy

[Alison Clough]

Is there a way to specify what issue type to use as default when creating a "story" within the plan hierarchy. We have a plan that pulls in project data that includes a number of issue types (epics, stories, incidents, bugs, etc.). When clicking the ellipse to create a story under an epic, for example, the issue type defaults to incident, not story. If you remember to change to story, it will remember it during the session. But, if you open the plan back up, it goes back to the default which is Incident. I read another article that suggested to filter the view to only show the desired issue types and that this would remove the option from the selection, but this did not work. Anyone have any other suggestions? 

[jengoree]

This is filed as a bug, for both Cloud and Data Center:
https://jira.atlassian.com/browse/JSWSERVER-21925
https://jira.atlassian.com/browse/JSWCLOUD-23338

You can add yourself as an affected customer by clicking 'This affects my team'.

[Irina Mosina _TechTime_]

Hi @Alison Clough 

That's a very good question and I would think that the order of Issue Types in the Issue Type Scheme would define that, but I don't think it's the case. Let me test it first and perhaps you can check on your end as well. To confirm that you need to be a Jira Admin capable of editing Issue Type Scheme. That's the screen you'd be looking at and it set's the order of issues in the Create dialog normally. 

To get there, as Jira Admin, for to Project Settings, Issues, Types, Actions (top right), Edit