Curious if anyone has the experience of dealing with a Jira admin that limits available issue types. The only options users seem to have access to are tasks and bugs. I feel like we should be taking advantage of the story type but its not available in the drop down when creating a new issue.
The list of issue types available is one of the project configuration items.
A project can offer one or many issue types to the people creating issues in it. For Company Managed projects, this is done with the "issue type scheme", which simply lists all the issue types you can use in the project, and for Team Managed projects, the list is local to the project and available in project admin.
You will need to talk to your admins about adding more types to your project(s)
This must be happening because the issuetype Story is not associated with your project. If you are a jira admin, try the following:
- Go to "Project Settings";
- In the "issues" section, go to "Types";
- Click on "Actions" and then click on "Edit issue types";
- Search and drag the "Story" issuetype to the project's issuetypes scheme
- At the end of the page click on "Save".
Once saved, the issuetype will become available in the "Create" options.
Thank you @Fernando Eugênio da Silva. I am not a Jira admin. Our Jira admin also happens to be our VP of Development. They manage all work assigned to dev team. I was just curious if anyone might have experience with this practice of not associating issuetype Story - before I ask our admin ;)