Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Problem with default ticket type in Jira Work Management?

Aline Veyradier
Contributor
April 2, 2024

Hello,

Since a few days, the default ticket type when creating a ticket from the table, list or timeline is "bug" (a priori the first in the list of types in alphabetical order).

However, the default ticket type in the ticket type system is "task" (see capture below).

For your information, this works correctly when the ticket is created from the "Create" button in the main menu.

Any idea how to correct this anomaly?

Thanks in advance

2024-04-02 12_15_03-Modify Système de type de ticket - Jira.png

1 answer

0 votes
Ste Wright
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 2, 2024

Hi @Aline Veyradier 

Default issue type is only one part of the logic - it's used in a new user session, or for new users who haven't created an issue yet.

The Issue Types are displayed based on this rationale...

  1. Most recently used issue type in user session
  2. Default issue type in the issue type scheme
  3. Ordering of types in the issue type scheme

 

So if a Bug is the last issue type you created, it will show as the "default" issue type in the next creation action. This is confirmed in this comment here.

Ste

Aline Veyradier
Contributor
April 2, 2024

Thank you for your reply, but it's not entirely satisfactory.

How then can you explain the different behavior depending on where the issue was created? Board, list, timeline ... or "Create" button ?

It seems that for these three views (board, list, timeline in JWM), the issue is created by default as a "bug", i.e. the default issue type is not applied ("task"). The first issue of the project has been created by default as a "bug", first issue type in alphabetical order.

 

Aline Veyradier
Contributor
June 24, 2024

I'm closing this ticket because I've just checked and the problem seems to have been solved.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events