Project Keys

[Jo.Clayton]

Hi, we renamed our board to one that was previously used by another team. We are now Digital Analytics (previously Digital Reporting) and the other team was Digital Analytics and they are now Measurement Solutions. The other team renamed their board from Digital Analytics to Measurement Solutions and they were able to update their key from DA to MS. Now our board has the correct name (Digital Analytics) when we try and update the key from DR to DA and we get the following error message: Project 'Measurement Solutions' uses this project key.
Anyone know how we can fix this issue? Thanks 

[EddieW]

Yes, you can use another excellent plugin from Jamie (same author as Script RUnner) the JIRA Behaviors Plugin - https://marketplace.atlassian.com/plugins/com.onresolve.jira.plugin.Behaviours

Docs: https://jamieechlin.atlassian.net/wiki/display/JBHV/JIRA+Behaviours+Plugin

Makes it trivial to set one field based on another right from the workflow config.

[Will R]

I'll play with this tomorrow... just installed it.

From desc sounds excellent!

Already has another feature I was wanting to implement but just accepted I couldn't "mandatory based on other fields"

Amazing.

Thanks Eddie

And Jamie.

[Will R]

Hey, so I started looking at this plugin today.

I'm not rally sure how to use it to do what I want. The documentation has some exmaples but they aren't what I'm looking for and I'm not sure how to modify to make it work for me.

Can you help me out a little with it?

In a parent task....

When issuetype ="x"

then set customfield1 = "y"