We use custom fields to effect an assigned team and watching teams based on Project. Before upgrading to 5.2.11 users would click the 'Create Issue' link and be asked about Project and Issue type before the main dialog for creating issues loaded. When this was done our customized defaults for these custom fields was prepopulated. The Project type was not mutable after making this selection. Now the user specifies the Project on the main dialog, and nothing triggers our defaults to load.
Is there a way to configure the behaviour of the 'Create Issue' link (not by writing a plugin) to achieve the prior functionality? or perhaps there is something to configure so that the change to Project will re-execute the configured Custom field defaults?
I am already using CustomField Context, so that will not help me solve this problem.
I suppose I am glad this issue is already reported as a bug (JIRA-30942), but what I am looking for is a way for the 'Create Issue' link to work like it did in JIRA 4.x where I had to choose the Project before launching the create issue display, and then I could not change the project after making the initial selection. I am looking for a way to configure it like this.
I will also accept 30942 to be fixed and made available. :)
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs