The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Custom Field Contexts and different defaults by project

Deleted user
May 22, 2014

Hi,

I've got a custom drop-down field called "Delivery Team" with

  • Team A
  • Team B
  • Team C
  • etc

I'd like the default team for each project to be different, and so had set up different contexts for each group of project, with the appropriate default team. However, I had to re-enter the list of teams for each context.

Now, something has gone very odd, since it seems to treat all of these options as being unique. So although an issue already says "Team A" if is a different "Team A" from the context it is now in, so when users it through the workflow the delivery team is disappearing! This is a real headache and difficult to clean up.

Is there a simple way to keep the list of options the same for each project, but just change the default? All these projects share a workflow, so I can't set it in there

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Deleted user
May 22, 2014

I've fixed the data by doing a series of very messy JQL statements and bulkk updates, but the question remains..

Is there an easy way to cahnge the default custom field value for a project, without having to set up a different context (and hence different options) for each possible value?

TAGS
AUG Leaders

Atlassian Community Events