• Type: Bug
• Resolution: Not a bug
• Priority: Medium (View bug fix roadmap)
• Fix Version/s: None
• Affects Version/s: 5.1.3, 5.1.4, 5.2.9, 6.0.2, 6.2-OD-5, 6.2.2, 6.4
• Component/s: Issue - Create Issue
• Labels:

  • affects-cloud
  • affects-server
  • papercuts

1. 

   issuetypedefaultnone.png

   21 kB

   28/Jan/2015 11:11 AM

2. 

   DefaultIssueType.png

   95 kB

   19/Nov/2012 5:01 PM

3. 

   CreateIssueDefaultType.png

   132 kB

   19/Nov/2012 5:01 PM

[JRASERVER-30620] Setting Default Issue Type to "None" Ignored

Andy Heinzer made changes - 24/Aug/2021 8:57 PM

Remote Link

Original: This issue links to "Page (Atlassian Documentation)" [ 220388 ]

ASweeten made changes - 15/Apr/2021 6:55 PM

Remote Link

New: This issue links to "PS-74736 (Atlassian Support System)" [ 544344 ]

Sergey made changes - 16/Feb/2020 10:48 PM

Link

New: This issue was cloned as JRASERVER-70655 [ JRASERVER-70655 ]

Bugfix Automation Bot made changes - 28/Mar/2019 12:08 AM

Minimum Version

New: 5.01

Owen made changes - 16/Oct/2018 12:52 AM

Workflow	Original: JAC Bug Workflow v2 [ 2831395 ]	New: JAC Bug Workflow v3 [ 2922656 ]
Status	Original: Resolved [ 5 ]	New: Closed [ 6 ]

Owen made changes - 25/Sep/2018 12:28 AM

Workflow

Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2593684 ]

New: JAC Bug Workflow v2 [ 2831395 ]

Ignat (Inactive) made changes - 01/Feb/2018 2:37 PM

Workflow

Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1521794 ]

New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2593684 ]

jonah (Inactive) made changes - 02/Apr/2017 10:11 AM

Description

Original: In order to force users select the correct *Issue Type*, is configured *Default Issue Type* as *None*, but when users click on create a new ticket *Issue Type* brings the last issue type selected instead of *None*, which means option *None* doesn't work as expected. If the user has never created a ticket before or just switched projects *None* will default to the top Issue type in the *Issue Types for Current Scheme*. To reproduce: # Login JIRA as Administrator; # Navigate trough *Issues >> Issue Type Scheme*; # Select *None* in *Default Issue Type*; # Create an user; # login JIRA with new user; # Try to create an issue.

New: {panel:bgColor=#e7f4fa}   *NOTE:* This bug report is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JRACLOUD-30620].   {panel} In order to force users select the correct *Issue Type*, is configured *Default Issue Type* as *None*, but when users click on create a new ticket *Issue Type* brings the last issue type selected instead of *None*, which means option *None* doesn't work as expected. If the user has never created a ticket before or just switched projects *None* will default to the top Issue type in the *Issue Types for Current Scheme*. To reproduce: # Login JIRA as Administrator; # Navigate trough *Issues >> Issue Type Scheme*; # Select *None* in *Default Issue Type*; # Create an user; # login JIRA with new user; # Try to create an issue.

jonah (Inactive) made changes - 02/Apr/2017 10:11 AM

Link

New: This issue relates to JRACLOUD-30620 [ JRACLOUD-30620 ]

Confluence Escalation Bot (Inactive) made changes - 20/Feb/2017 12:46 AM

Labels

Original: papercuts

New: affects-cloud affects-server papercuts

Load more older history items