John Funk Community Champion

Hi Jay - Could you give us some more details? Is it a Next-gen project? Classic Project? What type of board - Scrum? Kanban? Typically when your problem happens, the underlying workflow used by the board has been changed from a Simplified Workflow to a shared workflow. Therefore the only way to modify the workflow to add a…

Sorry, but I am not a Groovy expert either. That's why we switched to Automation for Jira. :-) Nor have I used those types of fields. I just use a standard Number field. 

Hi Andreas - Unfortunately right now you cannot have just one Done status for multiple Next-gen projects. You can go to Settings > Issues > Statuses to see when statuses use which workflows. Maybe that will help you decide on the right status. 

I think you will probably need to hope a support ticket with Atlassian as they can see into your system to see why some do not fire. You will need to provide them with an example or two of issue keys that should have fired but didn't. https://support.atlassian.com/contact/#/

Hi Amit - Welcome to the Atlassian Community! What does it say when you look at the Audit log for the rule? So does the rule NEVER run now? Or just in some cases? 

You rename the labels by editing the Transitions in the workflow. Can you post a screenshot of your workflow?

Hi Patricia, So if you go to this URL do you get the error? You have to replace the YourCompany part with your domain. https://YourCompany.atlassian.net/plugins/servlet/ac/com.codebarrel.addons.automation/cb-jira-automation-rules#!/

Simply drag the statuses with those "labels" to the Unmapped statuses section. 

Sorry, I lost track of the original discussion - the problem is that Next-gen does not currently handle Epics in the proper way like Classic projects. That is why it is failing to recognize the Epic. :-(

Hi Michal - No, there is no provision in Automation For Jira to allow for the creation of a Component on a project. 

You should check go to the Apps section to see. There is a Free Automation For Jira Lite app that should do the trick. Or this is a more robust paid app. 

Hi Mike, You can use Automation For Jira for that if you have the add-on. 

Correct!

Hi Alicia, You certainly can use Automation For Jira to set the Assignee based on a Transition. Not sure what you mean by "get credit". Not sure how you are measuring that. 

And you are sure that KARAT-2198 is an Epic? If so, try putting another Condition in front of that one for the Project Condition: If project = ABC Condition: If issue type = Epic

Hi @nina_schmidt - That was almost exactly like my first week back in the office last week. Thanks for sharing!! I love your sense of humor as well. ;-)

Perfect!!

Hi Markus - I don't use Scrum, but I typically have opinions. :-) Components are good for grouping issues for running filters, reports, etc. Some times even boards, but not necessarily. For instance, if you want to see all of the Front-end work you have done, you simply run a filter with: Project = ABC and Component =…

Great! Glad it is working for you now. :-) If this takes care of what you need, can you click on the Accept answer button to close this one out? Thanks!

Hi @Irène - You would use something like: {{issue.customfield_16943}+{{issue.customfield_16719}} But you would have to do that for one issue at a time. 

You would have to update the calculated field as soon as one of the values is updated. Then when you call the transition screen, it's simply displaying the value in the field, not calculating it on the fly. I don't have ScriptRunner or Server, but I assume you could use it to calculate the value. I would use Automation For…

Thanks @Andy Heinzer !

Hi @yeenfei - Let me see if I can get someone from Atlassian to help you out. 

Great! Glad it is working for you. :-)

You have to save the screenshot as a graphic file and then upload it with the camera icon. 

Glad it is working for you now. :-)

Verifique el esquema de Permiso para ver quién tiene acceso al permiso Examinar proyecto.

Very good - Holler back if you run into problems. :-)

Is this a custom field that you created? What happens when you click the Edit button? Finally, make sure that the Technical Answer field is available on the Edit screen used by that project. 

So it is working for you now?