Null value for selecting a project

Shailesh Dhawale February 5, 2020

When creating a ticket

I want a null value for the project system field

after that from the dropdown list, will select the required project

how can I achieve that requirement 

1 answer

1 accepted

0 votes
Answer accepted
Callum Carlile _Automation Consultants_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 6, 2020

Hi @Shailesh Dhawale,

This is not possible unfortunately, when you create an issue is needs to be associated with a project, as it needs the project's key to create the issue ID (e.g. ABC-1 for the first issue in the ABC project).

What you could do, is create a project called something like Pending Triage, and create issues in here that are to later be moved to another project, then these can be moved using Jira's 'Move' button and can be associated with another project. This would automatically update the issue's key to the key of the new project

cgadade February 13, 2020

Hi @Callum Carlile _Automation Consultants_ ,

when you create an issue is needs to be associated with a project, as it needs the project's key to create the issue ID -Absolutely correct,

   But our use case is,we don't want pre select dropdown under project field,while issue creation ,we want "Please select a project " then user will need to select project from dropdown and will  create an issue.Simply we want to ignore last used project which jira remembers while issue creation

Callum Carlile _Automation Consultants_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 13, 2020

Hi @cgadade, ahh I see what you mean - I assume this is so that issues aren't accidentally created in the wrong project, right? (very easily done ;) )

Unfortunately this is not possible in Jira, and there will always be a 'default' project in the dropdown menu, which is the last project that you created an issue for. I guess this is for the same reason as before, that you need to associate an issue with a project, so it was designed that way to save people time as they wouldn't need to select the same project each time they create an issue

cgadade February 13, 2020

Hi @Callum Carlile _Automation Consultants_ ,

  I assume this is so that issues aren't accidentally created in the wrong project, right? (very easily done ;) )-Correct

 Thank you so much for your prompt response ,Do you have any idea about new feature of Atlassian ,are they going to add this feature in ongoing versions?

Callum Carlile _Automation Consultants_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 17, 2020

@cgadade I'm afraid I'm not sure whether or not Atlassian are going to implement this in the future, but I feel like it's not the sort of thing that would be implemented, based on how the software tends to favour default items rather than leaving anything blank.

If there's something you would like to see implemented, you can raise a feature request with Atlassian here and see what they get back to you with :)

Suggest an answer

Log in or Sign up to answer