Our company has two projects that we use most often connected to Salesforce, however one of them is used more, but because its alphabetically last we have to select it each time and that takes time when creating a lot of issues.
We have even considered removing the mapping all together to the other project just to save time and just readding it as required or using the one mapping and then migrating the issue in Jira from Project to Project afterewards
Also would be fine (with our use case) to at least define the default as an "Admin" (we have one project that gets sorted first that is rarely used for any support cases from Salesforce and as a result all support personnel have to change the project selection).
Sam Gatica
+1
Attachments Open full size
Agree with Derrick. +3 upvote.
Attachments Open full size
Need to be able to specify Default Project AND Default Issue Type
Attachments Open full size
Our company has two projects that we use most often connected to Salesforce, however one of them is used more, but because its alphabetically last we have to select it each time and that takes time when creating a lot of issues.
We have even considered removing the mapping all together to the other project just to save time and just readding it as required or using the one mapping and then migrating the issue in Jira from Project to Project afterewards
Attachments Open full size
Please consider this. Having a less active project as the default has caused a number of ticket snafus that have decreased our productivity.
Attachments Open full size
Also would be fine (with our use case) to at least define the default as an "Admin" (we have one project that gets sorted first that is rarely used for any support cases from Salesforce and as a result all support personnel have to change the project selection).
Attachments Open full size