-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
7
-
Problem
When moving a Project of an issue type to another Project, the default dropdown selection issue type could change to a different type which can create accidental inputs from users.
Suggested Solution
The default Selection type should be the same as the current issue being moved, or allow for this setting to be configurable.
Why This Is Important
It will help prevent accidental input from users that could change an Issue's Type. (e.g From a BUG to STORY) that could delay projects
Workaround
This setting seems driven by the Default Issue Type chosen for a project
- Navigate to Jira Adminitration>Issues
- On the Left, choose Issue Type Schemes
- Find the Project or Default Issue Type Scheme to change and Click Edit
- Change the Default Issue Type to "None" or any other desired Default Value
- Click Save
- links to
[JSWSERVER-25519] When moving ab Project of a issue type to another Project, the default dropdown selection issue type could change to a different type.
Labels | New: ril |
Support reference count | Original: 6 | New: 7 |
Labels | Original: ril |
Support reference count | New: 6 |
Labels | New: ril |
Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 979822 ] |
UIS | Original: 1 | New: 0 |
UIS | New: 1 |
Description |
Original:
h3. Problem
When moving a Project of an issue type to another Project, the default dropdown selection issue type could change to a different type which can create accidental inputs from users. h3. !image-2024-01-25-20-05-03-081.png|width=774,height=251! h3. Suggested Solution _The default Selection type should be the same as the current issue being moved, or allow for this setting to be configurable._ h3. Why This Is Important _It will help prevent accidental input from users that could change an Issue's Type. (e.g From a *BUG* to {*}STORY{*}) that could delay projects_ h3. Workaround This setting seems driven by the *Default Issue Type* chosen for a project # Navigate to {*}Jira Adminitration{*}>{*}Issues{*} # On the Left, choose *Issue Type Schemes* # Find the _Project_ or Default Issue Type Scheme to change and *Click Edit* *!image-2023-11-27-13-36-07-980.png|width=566,height=281!* # Change the Default Issue Type to *"None"* or any other desired Default Value # Click *Save* |
New:
h3. Problem
When moving a Project of an issue type to another Project, the default dropdown selection issue type could change to a different type which can create accidental inputs from users. h3. !image-2024-01-25-20-05-03-081.png|width=774,height=251! h3. Suggested Solution _The default Selection type should be the same as the current issue being moved, or allow for this setting to be configurable._ h3. Why This Is Important _It will help prevent accidental input from users that could change an Issue's Type. (e.g From a *BUG* to {*}STORY{*}) that could delay projects_ h3. Workaround This setting seems driven by the *Default Issue Type* chosen for a project # Navigate to {*}Jira Adminitration{*}>{*}Issues{*} # On the Left, choose *Issue Type Schemes* # Find the _Project_ or Default Issue Type Scheme to change and *Click Edit* !image-2024-01-25-20-06-27-793.png|width=651,height=308! # Change the Default Issue Type to *"None"* or any other desired Default Value # Click *Save* |
Attachment | New: image-2024-01-25-20-06-27-793.png [ 450528 ] |