-
Suggestion
-
Resolution: Unresolved
-
36
-
28
-
Unfortunately, in light of more urgent priorities, our team is not working on this feature anymore. We know this will disappoint many of you and is not the answer many of you were looking for. We’ll let you know when we are ready to begin work on it.
Problem Definition
Currently, it's not possible to define a default issue type in team-managed (formerly next-gen) projects. The selected issue type will be the last issue type used by the user. Considering different users may use different issues types, there will not be a "default issue type" defined to all users
Suggested Solution
As a team-managed (formerly next-gen) user, I want to be able to define a default issue type in the project's settings to make sure all users will have the same issue type selected.
- is duplicated by
-
- Closed
- is related to
-
- Closed
- was cloned as
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-87186] As a team-managed user, I want to be able to define a default issue type in the project's settings
+1
What's the sense of this Setting if it only applies once when the user creates the first ticket.
Default issue type should be applied to the creation screen for all attempts of creation.
+1
This morning I adressed this issue in kind of a rough way:
- I wanted Bug to be the default issue type in our project.
- I deleted all the other issue types in project. Had to bulk edit few of the issues from Task to Bug, as the system did not let me delete Task before that.
- When Bug is all that's left (besides SubTasks), it acts as default. Even when I returned the Task issue type, Bug still holds as default.
If it will work permanently is yet to be discovered, but so far it works.
I would highly prefer "default issue type" to be for every new issue created. With how it is now, there isn't even a point of having it as a setting.
This feature request is 4+ years old?
Hi there!
Sorry if I sound rude but this seems kind of a basic functionality of any "ticket management" system that allows creating different types of them.
It has been reported in 2019 and we are in 2023 .... so a bit more than 4 years ago.
Can we hope for an update or priority change for this issue?
Otherwise, we will have to go through the effort of moving to "company managed" with all the restrictions it includes.
Please, please consider this issue 🙏
Users adding wrong issue types on a project and they make a mess. Very much needed feature 
If I'm importing tenable scan results they end up with issue type "Story" - whatever... the cultural impact of calling every vulnerability a "Story" instead of a "Bug" is ridiculous!
Import process throws an error saying no issue type was selected so it's going to use the default issue type (which in my case, for no clear reason, is Story).
So I got rid of that issue type and solved my problem. But I agree with previous commenters that this limitation seems, on the face of it, to be silly.
This is still a needed enhancement! We have so many projects within our team. For the kanban/teams managed projects tasks are our default issuetype. We need to be able to change the default issue type. Please put this back on the active list. thank you! Jean
Bad ideas are
Bad enough; Bad ideas
Half built are much worse.
I can sort of see how the theoretical concept of a "team-managed project" could be a not-terrible idea. However, what we got is not even half-baked; it's a bunch of unmixed eggs and the wrong kind of flour in a bowl.
You need to actually think this stuff through before you release it. Ideally, talk to some people who use Jira daily and who would be impacted by whatever thing you're thinking about.
Please add this one, creates lot of frustration and wasted time for the team!
Not having this really messes us up. We cannot add or remove ticket types with the default ticket type changing. This is SUPER FRUSTRATING (same as the lack of hotkeys).
I spend hours per day in Jira and the inefficiency of NextGen/Team Managed is killing me.
Sure this looks shinier, but as a power user, the last 2 years Jira has gotten worse in many ways... But I kinda have to switch since I expect none of the issues I had with the old Jira wont be fixed ever.
Please add this feature to reduce the pain a little.
Another requirement completely ignored from the backlog that people are waiting for. This is a waste of time voting for these issues, Atlassian just want to add features to put on marketing presentations, they are not interested in making the product more usable.
please upvote this! It's wild that I can't create a default, and have to CONSTANTLY change Issue types to Story, when we are mostly creating stories. Seems like an easy feature to implement
Upvote!
Also found a probable workaround:
I wanted to set "story" as a default epic child issue type instead of "task" In the kanban-type project. So I deleted the "task" issue type in my project configs, which switched child type to the "story" type. After re-adding the "task" issue type, this config seems not to be affected, so the default child issue type on a new epic is still "story."
Upvote, please!!!! I just recommended this as a lightweight way to log bugs but it will be confusing if it keeps changing back to story.
Yes please. It is annoying to have to switch the issue type to "Story" every time and again you create a new ticket.
we definitely are longing for this feature. It is annoying to have to switch the issue type to "Story" every time and again you create a new ticket.
Add another vote here. Our team makes use of a set of custom fields for every User Story we write. It would be very useful to be able to set a custom issue type as the default. Additionally, making the type available and default across multiple next-gen projects would be very handy, though I realize that's a different feature.
This is really a must feature when we want to give the Jira access to the end user for creating Tickets. Please expedite.
Ditto the above. We waste a lot of time during sprint planning having to move "tasks" to "stories" as our issues creators create issues quickly and don't switch the type from "task" to "story"
Whatever I do, every time I create a new issue on the next-gen board, its type is a user story. At the same time, our team creates tasks more often and it is very inconvenient to change the type of task each time. In addition, some team members can skip this step and create a default task type - the user story, while the name and content of such a task, of course, does not correspond to the user story.
I second this request!
The majority of issues created on behalf of the customer will originate from phone calls to our level 1 agents, which we set up as a new incident type.
Phone calls can be pretty rapid fire, and not having to select the issue type every phone call would be a nice QOL and time saver for our level 1 team.
This was possible in the Classic project type, so hoping for this feature to return
+1