David Leal_28ge8x Rising Star

Thanks, @Alicia Peebles for some reason I didn't see that option. Now I changed it. Thanks a lot!

This is a good solution @christopher_douglas, but it only solves to calculate the time flagged overall, which is useful, but provides partial information, since the flag feature can happen on any status, you loose that information. Following this approach to identify the time flag on every status, then it will imply to…

@Tim C I see, I guess you are referring to some feature only available for Jira Admin, I am just Jira project admin. I will check with my Jira admin. The only option I have is from the list of rules, click on the ellipsis (top right) corner then select: View performance insights, but the view doesn't show what other rules…

Thanks @Tim C that was my first assumption "timing", but the previous successful execution was at 2:14PM and the first railed execution was at 8:09PM, so there is enough time. The refetch action, has no parameters, and as per my understanding the scope is within the rule only, so invoking it before transitioning won't have…

For example just looking to one issue (subtask) that executed successfully several times and then failed. Here the information with the time stamp. This is the issue history: Here is the log information in the automation rule: then the failed execution: as you can see the rule executed correctly three times for the same…

@Boldizsár Vermes thank for taking the time to review my question. We only allow transition to the next status, there is no way to go from previous status to DONE, we don't allow such transition. It happened only when the rule failed, and it was not possible to roll back the transition, so the user continues until to reach…

@Tim C at the end I asked my Jira Admin for help and we implemented validator in the workflow. This is more stable, and allows to send a popup message advising the user why the transition is not allowed, so I disabled the rule. I logged the status value, actually I added a condition before roll back the transition to make…

@Tim C thanks! This is a good advice, but then I depend on my Jira Admin, whenever I can, I try to solve it using Jira rule. The thing is that I was not able to find the pattern when it fails, other than it happens usually after a success execution, and the user latter tries again to transition the issue being unassigned.…

Well, the rule assumes the epic exists you need to link an existing epic on creation. The rule is triggered when the child issue is created. Did you try to log the information (Log Action) to see what is entering into the rule, to have more information.

 @John Gooch yes, it works for the current user, but I don't think it works for other that the current user executing the JQL.

@Vasilisa Yermakova for this case in a similar way: The rule is triggered when an issue is created, then you check it is not an Epic and it has an Epic linked, then you update your field (in the sample I use component) to update the field based on the corresponding Epic value. The condition Epic exists is the following:

@Vasilisa Yermakova sorry for the delayed response, I was busy, so basically what do you want when the epic changes the value for a given field, then you want it to propagate down the the corresponding child issues, correct? I have a similar rule to this one, that I think is can help you for your purpose: Lets say you want…

Please the details of the Edit issue field and also what exactly you want to achieve with the rule, it is not clear to me from your question. Thanks.

Thanks for your post @Ignacio Pulgar The ticket JSWCLOUD-17127 is from 2018 and this post from 2021, as of now, Atlassian hasn't provided a solution

@Akash Panchal I don't think you are going to achieve what you want. The trigger condition is on real time, then the JQL will apply to all the universe of issue that satisfy the condition, not a condition for the triggered issue. I would say there are two issues here: 1. The trigger condition, should not base on issue…

Have you checked the nature of your custom field? Are you sure is it a date?. It could be a date in string format, but not a data data type. Try to invoke a date function in your custom field to see if it really a date. For example: {{[date].plus[Unit]([number])}} For example: {{customfield_10008.plusDays(1)}} and to log…

I guess you can create a Schedule rule as follows: The JQL should be more precise: duedate != EMPTY AND duedate < -7d AND status not in (Done) Then define the email notification as follows: You can play with that to adjust it to your specific needs, I guess you get the idea. I hope it helps, David

Please share your attempt in Jira Automation, so we can understand better the scenario. Thanks

withHour is expecting a number, did you check your {{hours}} variable stores a number? (for example isNumeric()) Please share your automation rule. Thanks

Would you share your rule? how do you plan to trigger the rule, Since your scale is minutes, do you mean to schedule the run on every minute? I don't think it is possible. The minimum is 5 mins, and you would lose tickets since you are looking for exactly 40 minutes.

You can try Jira Cloud for Excel/Google Sheets, they are Atlassian official plug-ins and they are free. You can get the field Days in Status to get durations on a given status. Check for example: Jira Cloud for Google Sheets Add-ons Days in Status field pattern and returned value for duration. You need to know the status…

Thanks, @Bill Sheboy good idea, it would require converting the input string into a list first via split(",") for example.

It seems to be a bug as per this link: JSWCLOUD-25392.

@Jack Brickey Now it is working reasonable for Excel online, but I didn't do any change. I opened the file several times and also tried to open from the desktop and at some point it worked. If the problem continues I will open a support ticket for sure. The reason I am asking is because this question is from Sept, 2021, I…

As of today, Sept 4, 2023, I having the same issue @Paul M. Brunner. It looks like it hasn't been resolved yet. I have been dealing with this issue for more than a year. I found that using Excel online is more robust than using Excel Desktop. Excel Desktop crashes quite often, and I have been in situations where I cannot…

Great solution from @Bill Sheboy, but I think it is possible to remove components without creating a custom field. Interesting question @Michele D_Adamo actually I had to face a similar problem. Here is a more elaborated rule, based on my real scenario, which serves to add and remove components. Here is the scenario: *…

@Bill Sheboy, @Timo Vertanen smart solution, I am just wondering why we cannot use add/remove, I haven't tested it, but according to Advanced field editing using JSON. In the section Supported Fields and Operations, it stays: If you’re creating or editing issues, you can query a project’s createmeta or an issue’s editmeta…

@Jehan Bhathena correct, that was the issue, I was looking for some more complex errors related to the smart values, without looking at the obvious. 

Thanks @Bill Sheboy for your help on this. Do you mean I didn't add a space after in and I put user.Inputs instead of userInputs? I tested also the following: labels in ({{userInputs.remLabels}}) but I am getting the same error. Yes, it is a list of values, but at this point, since it is a user input from a manual trigger…

@Darryl Lee yes, what worked is your solution for example (adding # mark and removing the braces for userInputs.team): { "fields": { "customfield_10100" : { "id": "{{severity.get(issue.customfield_10262.id)}}"}, "customfield_10101" : { "id": "{{type.get(issue.customfield_10264.id)}}"}, "customfield_10103" : { "id":…