-
Bug
-
Resolution: Fixed
-
High (View bug fix roadmap)
-
7.2.9, 7.3.6, 7.3.8, 7.4.2, 7.6.9, 7.12.3, 7.13.2, 8.13.13
-
7.02
-
20
-
Severity 3 - Minor
-
32
-
-
Summary
The configured default issue type is never taken into account. The latest issue type used to create an issue is always set as the suggested choice even if you start a new session in a different browser or in an incognito windows.
This is not working as documented:
- Associating issue types with projects:
Set the Default Issue Type for the new scheme from the drop-down list. Please Note:
- The 'default issue type' is the issue type displayed in the selection-box when a user creates an issue.
- The issue types in this list depend on the issues in the Issue Types for Current Scheme list on the left.
- The None option means that there is no default value. If this option is selected, the system will show the first Issue Type listed in the Issue Types for Current Scheme.
- The Issue Type is remembered as long as you keep creating issues in the same project. Once you change projects or log off the system, it goes back to the default value.
- How to change the default issue type displayed at the Create Issue screen
- The next time the user creates an new Issue, the last issue type used will be displayed. ----
JRASERVER-30620 - Once a user has created an issue in a project in the current session, JIRA retains the issue type from the previous issue any time the user creates a new issue in the same project. This is intended to make it easier for users to quickly create issues, such as when a software developer is creating a number of stories for a sprint or a QA engineer is filing bugs.
- The next time the user creates an new Issue, the last issue type used will be displayed. ----
Steps to Reproduce
- Create 2 projects (e.g. SPA and KPA) having 2 different issue type schemes associated
- Modify the issue type scheme of SPA to have default issue types set as Bug and move it to the top of the list
- Modify the issue type scheme of KPA to have default issue types set as Task and move it to the top of the list
- The result looks as below:
- Click on create... see that the default issue type is not taken into account (by default you get KPA as the project and Bug as the selected issue type, see below screenshot):
- Create an issue type Story in SPA
- Click on Create to create a new issue. Select KPA. See that Story is selected by default. Create a Story in KPA as well
- Log out.
- Open a new browser or an incognito window and log into the instance again.
- Click on the Create button
Expected Results
The default issue type for the project is selected
Actual Results
The issue type used in the previous session is selected (Story). Please notice that also what happened in Step #5 is not working as documented.
Notes
This behavior reproduces consistently and has been tested on clean installations of JIRA 7.2.9 and 7.3.6.
The only time the default issue type is taken into account is when, for example:
- You create an issue in Project A of type e.g. Task
- You create a new issue and select Project B
- The issue type Task does not exist in Project B and therefore the default issue type is selected instead
Workaround
There is currently no workaround for this issue.
- is duplicated by
-
-
- Gathering Impact
-
-
-
- Gathering Impact
-
- is related to
-
-
- Closed
-
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRASERVER-65439] The default issue type is not taken into account
The issue is still present in 9.12.2 version.Hi e54952ea462e, we usually wait around two months before backporting bug fixes into the LTS. Based on that, LTS fix release should be expected around end of July.
Kind regards,
Grzegorz
00379afc8394 any idea when it will make it into the LTS? or how long can we expect before 9.10.0x code makes it to LTS??
Dear Customers,
We're happy to announce that this issue is fixed in 9.10.0 release.
Best regards
Grzegorz Kulinski
Jira DC developer
Please prioritize this bug. It's very problematic for the users and more for the service teams
Hi! I'm facing this problem with my team. As it is a service team, the impact on the day-to-day is considerable, as users open requests incorrectly and the team needs to correct them right away.
I need a solution, the whole team and I are having this problem, I would be grateful if this happens as soon as possible.
Kind regards,
Bruna
Im not sure what theyre gathering, this is a huge problem. What this means is tickets do not get routed correctly based on issue type and the actual users request. Which causes delay's since the the ticket doesnt get routed to the responsible party that is correlated to the user request.
Hello,
Please implement it.
We are eagerly waiting for this feature.
By nature if we have to see (We are able to set default issue type like (Story, Task, etc). But its work only first time. If we will try to change project and then try to create new then it will take previous historical issue type.
It means providing default issue type setting in configuration no more applicable.
Thanks
Any update on when this will be addressed? This issue and associated watchers are probably in the hundreds by now, it seems important enough that enough people have come across it and would like it have this behavior.
Dear Atlassian,
We all know you have an amazing sales force; they probably could sell ice to those living at the poles. Just image if your development team were that skillful - what it would mean! No one submitting these annoying issues, common sense prevails, and everything works.
Why not change the Default Issue Type from a selection list to a cascading list with the first selection list including options: Use on initial issue creation., Use on all issue creations. The second list include all issue types for current scheme, plus 'None'. With the Issue Type field being mandatory; if issue type scheme is configured to Use on initial issue creation then user is forced on each new ticket to choose issue type and if configured to Use on all issue creations then user is only forced to choose issue type for the first ticket and Jira operates as-is for all new issues. I don't think this is rocket science!!!
Hi, I would like higher priority on this. Our problem is that people reporting an issue tend to pick the default unless required to make a selection. We are making statistics that are being reported up in the organization and it is difficult to make the parts based on issue type correct. We would like to have a way to have 'no default' to make the reporter consider what type of issue it is.
Thanks!
Please status? This is a big problem for many companies using Jira.
Many thanks!
When performing one of the labs for the course "Agile with Attlassian Jira", I came across this:
"3. In the upper-right corner, click Actions, then select Edit issue types.
4. Notice that the default issue type is Story . This is the issue type that will be selected by default when
you first create an issue. View the order of the issue types under Issue Types for Current Scheme. You
can rearrange these to change the order of the types in Jira dialogs."
The above mentioned lab does not specify that the issue type for the project will be selected by default ONLY when
you FIRST create an issue.
This is misleading for new users.
Our enterprise organization has the perspective as Dwight ^. Get this fixed ASAP.
As noted before (I have voted for JRASERVER-30620 and JRASERVER-15213), different teams want their issue management system to suit their needs. By resolving this bug it would make JIRA better for administrators and users.
Unlike Chandramouli I have no sympathy for Atlassian's perspective. The current functionality is poor because it is unintuitive/confusing for administrators, and does not provide the flexibility an enterprise-grade issue management system should. JIRA provides so many rich configuration options, I do not see any argument against adding a project option for this (even if it is an extension of the current 'feature').
We have thought carefully about our issue tracking workflow and continue to adjust it based on usage and experience. For some JIRA projects we want the Create Issue screen to use a specific default Issue Type, and for users to change the Issue Type during/after some investigation.
Since JIRA cannot currently do this we were forced to add custom workflow validation which:
- Is an example of added admin overhead we could have avoided.
- Means that in cases when the issue creator knows the Issue Type they cannot set it until after they have logged the case. Which adds user friction.
I think someone at Atlassian needs to climb down from their high-horse and get on with providing what the customers ask for.
Total votes for the issues so far:
JRASERVER-30620/JRACLOUD-30620 = 60 (each?)
JRASERVER-15213 = 7
JRASERVER-44026 = 1
JRASERVER-44632 = 3
JRASERVER-40898 = 1
JRASERVER-65439 = 11
JSWSERVER-11749 = 2
IMHO the root cause of all of these is the same.... are there others I haven't found?
If nothing else by resolving this issue you would reduce the effort by Atlassian staff to log and curate all of these issues... but given this (latest) duplicate was logged over 2 years ago and has not yet been resolved I know someone is still comfortable in their saddle.
We use Jira 7.13.2 and the issue still persists.
I need to set a default issue type (example Task) for a particular project. I tried to create an Issue Type Scheme and set the Default Issue Type as Task. But still it does not show the default issue (Task) when I click the Create button.
I understand the below point from Atlassian's perspective:
"The current Jira behavior is that the default issue type will only work for the first time when the user login and try to create a new issue. Once a user has created an issue in a project, JIRA retains the issue type from the previous issue any time the user creates a new issue. This is intended to make it easier for users to quickly create issues, such as when a software developer is creating a number of stories for a sprint or a QA engineer is filing bugs, etc."
But providing the Default Issue Type option is of no use because of the above feature. Kindly provide a solution for this issue.
Antonio.Garcia1881397977, Can you kindly create a support request in support.atlassian.com so that we can have the issue further investigated by a Cloud support engineer (and, in case, a bug ticket raised for Cloud as well).
Thanks,
Dario
This bug is not fixed