Request Definition When Creating a New Component in a Ticket

[Mercedes Rothwell]

Components are an excellent tool. However, they become easily muddied. This morning I had to clear out two components that users created by mistake. The first user typed into the incorrect field, then clicked into the correct field. The other user tried to click the search result that matched what they typed, but missed and clicked out of the field.

Clicking out of the field causes the changes to save. This creates a component in the system that remains even if the person corrects their mistake.

Today is not the first time this has occurred, nor do I think it will be the last. However, I propose a solution.

When a person types into the fix version field and that version does not exist, a window comes up requesting the person add a definition in order to create the version. You can exit out of this window if you made a mistake, and it will not create that version.

This would be an excellent change because:

1. It would reduce the number of components created by mistake.

2. The added definitions would assist component managers and other users identify the purpose of the new component.*

Note: I know that components already have a description field, however, when components are created by typing in the ticket, the description field remains blank.

[Jack Brickey]

Hi @Mercedes Rothwell ,

I checked for a suggestion in Jira.Atlassian.com product feedback but did not see anything. You might wish to use the in-app feedback located under the "?" Icon in the menu bar.