John Funk Community Champion

Hi Roberto, We do something similar and below is an example. There might be a more efficient way of doing it, but I created a Branch for each value in the Severity field (in my example it is the Impact field). Then I use the numeric value in the calculation of the Importance (in my case, Risk Score). Hope that helps.…

Hi Wilson - Welcome to the Atlassian Community! You should check directly with the vendor to see if that might have that on their roadmap. Or they could give you more information. Also, not sure if the ScriptRunner Behaviours app would be able to do that. Again, you should check with the vendor - probably before installing…

You clicked on the status. You need to click on the transition. That’s the line going to the status.

can you share a screenshot for when you click on the transition?

Hi Kiran, Check to see if there are any Conditions on the transition to Done. Also, check to see if it uses any transition screen with the transition to Done. 

Yes, the due date needs a value. Run this query in the Search/Filter area to see if there are results there.

Hi Katherine - Welcome to the Atlassian Community! You would need to create a custom Date field to capture the original Epic due date and populate it when you create the issue to be able to compare to the current Due date. 

Hi Chaitanya - Welcome to the Atlassian Community! Project = ABC AND DueDate > startOfWeek(-1) AND DueDate < startOfWeek()

Hi Kristian, I suspect there is something set on your board like a quick filter or sub-filter or something like that. Can you share some screen shots with appropriate details? 

No you will not lose your rules - not sure who has told you that, but it is not true. 

You use the old workflow editor.

Hi Rinat - Welcome to the Atlassian Community! Can you share the email that you got? 

Hi Peter This is a symptom of using Team-managed projects. Technically, those projects are completely isolated from each other. So when you create a workflow for one project and use the In Progress status in that project, and then do the same in another Team-managed project, then those 2 are really two different statuses.…

Yes, have you tried to drop the .id and just use {{priority}} or {{issue.priority}}?

Correct - Team-managed projects will not use these. https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/ See the line in blue. 

Right, which is why it is best for you to give it a shot first and post a screenshot of your rule so we can tailor the answer to your case. :-)

Hi Luisa - Welcome to the Atlassian Community! Try using the custom field value for the Priority field instead: {{fields.customfield_0000}} Where 0000 is the ID of your priority field. 

Thanks for sharing! I am thinking maybe it's the double quotes on the outside of the outside part. You wouldn't use those with a variable so probably not here either. Maybe take those off and try again. The inside ones should be good because that's what is used when the log returns a value. 

Free licenses don't expire. That will last as long as you keep using the product. Where you see the words summary or issuetype above, those are the field names. It is just that they are system fields so they look a little different. You should use the EXACT name of your field there, including case. 

This is very helpful for me as well. Thanks for sharing!

Excited to see all of the new things coming!

Sounds like you ran around the house 3 times to get in the back door. But glad it is working for you!

It is coming in May. 

I don't know the answer to that. Just that there is another option to accomplish what you want right now. 

Hi Suyambi - Welcome to the Atlassian Community! Can you give us an example of what you are wanting to see on the dashboard? All dashboards in Jira are basically dynamic. 

Understood, but you didn't answer my question. How are the two issues currently getting linked and when? 

@Jar Lady - I would suggest giving Bill's suggestion a try and then post a screen shot of your rule so that we can further help troubleshoot. Bill is the GOAT of Automation Rules so don't just discount his suggestion without trying it first. 

Hi Mark, Can you share the rule that you have? Especially where it shows the log of the value for the asset object. Also, that seems strange to me to store that value in an asset object. What not just a regular field? Or maybe try creating a variable based on the object, then use the variable in the formula. 

Hi Doods, You most certainly will not be able to do that out of the box with Jira. And not sure about any apps that might do that. Maybe ScriptRunner Behaviours. 

You are welcome!