Hi everyone,
I created a new Issue Type "Request" and would like to add this new type as a child-issue option in the Epic-issue, so that the user has one more issue type option (=Request) to choose from besides the predefined options: task, story and bug:
I already checked the "Issue type hierarchy", but this doesn't seem to be the right admin page since it didn't list the types "Bug" and "Task" (which is shown above in the dropdown).
Where is the parent-hierarchy of "Epic" (to its children: Task, Bug, Story) defined, and can it be extended by additional Issue Types?
Thanks!
Hello @Manju
The default issue hierarchy has three levels
Epic
|-- standard level issue types (i.e. Story, Task, Bug)
|-- subtask level issue types
When you create a new issue type you can create it either at the standard level or at the subtask level.
After creating the new issue type, if you want to use it in a project then you have to make sure that issue type is part of the Issue Type Scheme that is used by that project. I am guessing that is the step you have not completed.
Go to Project Settings > Issues > Type. That should show you a screen similar to this:
If you don't see the Request issue type listed there then you will need to click on the Actions button and select Edit Issue Types, and add the new issue type to this scheme.
Note that if this scheme is used by more than one project, the new issue type will become available in all projects that use the scheme.
This all assumes you have created the Request issue type at the "standard" level, and that you are using a Company Managed project.
Hi @Trudy Claspill ,
Thanks for the quick response. I already added the new Issue Type to the Issue Type Scheme of my project. But that does not correlate to the Epic hierarchy depicted in my first screenshot.
Just to clarify: my new Issue Type already shows up in the "Create Issue"-Dialog in the Issue Type dropdown (and yes, it shows up in all of our projects that use the same Issue Type scheme), but I need it to be inserted to the Epic-hierarchy (besides Bug, Story, Task), how do I do this or is it even possible? Your answer referred to the Issue Type scheme, which was already solved.
Thanks a lot!
Manju
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you working with a Team Managed project or Company Managed project?
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.
I am not able to recreate your scenario.
I created a new standard issue type - New Feature at hierarchy level 0.
I did not explicitly add it to the issue hierarchy.
I added it to the Issue Types scheme that is used by the project.
I created a new Epic issue in the project, and I do see the new issue type as an option for the child issues.
If your setup matches mine, then I recommend that you contact Atlassian support directly for additional assistance. And it would be great if you report back here what you learn.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Trudy Claspill ,
Thanks alot for your support. I tried your test case and it worked now. Sorry, it was my mistake, I checked already existing epic-issues and in their dropdowns the new Issue-type didn't show up (we have to change older Issues to the new Issue type and some of them belong to epic issues as childissues, therefore I checked how we can change these realtionship and noticed that the dropdown didn't offer the new type).
So everything works fine and the new Issue type is available for new Epic issues! Thanks alot for her help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.