Bill Sheboy Expert

One big challenge is JQL is not a SQL...and so all of us regular customers do not know exactly how it is performing comparisons of things like datetime types. Instead we must assume date comparisons are accurate when like fields are compared. (Aside: that is apparently not true for some things, such as related to history…

Hi @Makai Baker Rather than use the branching/conditions, you could try using the new Lookup Table feature of rules. This would work as long as you have 20 items/rows or less. Please look here to learn more and see examples of that rule…

Hi @Simon (AcesoMed) I recommend contacting the marketplace vendor for that app to learn if there is some condition where rule initiated events are not caught/used. And, perhaps a work-around might be to use an issue trigger within Jira and then to call their REST API from the rule. The vendor will know better on that one.…

Hi @Chris F Adding to Trudy's answer... You may want to check if you have any marketplace addons for dashboard gadgets. Many of those support creating velocity charts, and are more configurable than the built-in chart. And if you do not have any, there are often free ones (even for your Premium license level) that could…

Hi @V N Raju Raju Adding to Trudy's answer...If you have not started your rule yet, please review these documentation sources to create your rule, and if you have challenges, post images of your rule and audit log so the community can help. Information for version fields in…

Hi @Benny It appears there is a new defect for this symptom, which I recommend watching/voting for to see progress: https://jira.atlassian.com/browse/AUTO-805 Kind regards, Bill

Hi @Brad Rutledge -- Welcome to the Atlassian Community! I suspect that if you review the error message, you will find it is for the Summary field, which does have a character limit. My understanding is there is no work-around for that field. The Summary is intended to be a summary name/title of an issue. For more details…

Hi @Babak Hosseini I am curious...Would you please explain the purpose of this board? Jira boards normally reflect a process for a team to delivery something, from start to end. You instead seem to be describing the board as a list of things meeting some criteria. There are other features in Jira which teams often use for…

Hi @[deleted] First, your math expression in the edit is missing one of the curly brackets. Those should appear in pairs, so try updating that. Next, when using text values and variables in math expressions, rules sometimes need help with the type conversion. To do that, please use the asNumber function to convert them…

Hi @Pratibha Tambakad For a question like this, please post images of your complete automation rule and the audit log details showing your rule execution. Those will provide context for the community to offer suggestions. Thanks! Until we see those, I suspect the answer is "maybe"... The {{issue.issueLinks}} smart value…

Hi @Corne Cloete Would you please post images of the complete rule you have tried thus far, including details of the email action body, and of the audit log details showing the rule execution? Those will provide context for the community to help. Kind regards, Bill

Hi @Mee Soo There is no built-in function to do that. Instead you could chain the operations, such as: {{issue.description.replace(userInputs.oldValue1, userInputs.newValue1).replace(userInputs.oldValue2, userInputs.newValue2)}} Kind regards, Bill

If you are trying to send the email to users referenced in the newly created issue, your two options are: * Reference that issue's fields, such as with {{createdIssue.assignee.emailAddress}} * Branch to the most recently created issue, and send the email from inside of the branch. That will allow reference the the fields…

Hi @dallu divya That may not be possible, as you describe it... JQL finds issues, not any data stored in Jira. And if your versions are not yet associated to an issue they would not be available. One possible work-around would be to call the REST API to gather all project versions, and examine the ones which have/do not…

Hi @Lindsey Schaper -- Welcome to the Atlassian Community! Which checklist addon are you using from the marketplace? Knowing that may help the community to offer suggestions. Or...do you mean inserting a checklist in a text field using the markup syntax? And for a question like this, please consider posting images of your…

Hi @[deleted] Have you tried adding a clause to the JQL to exclude the trigger issue, such as: AND key != {{triggerIssue.key}} Kind regards, Bill

No, that should have no impact: you can send an email at any point in the rule. The only limitation is if you want issue data/fields in the email, you want the email action at the correct location in the rule to "see" the issue.

Until the histories show more information about rules changing issues, you can try this: Hover over the issue history to get the date/time of the changes, and then view the global automation audit log for that date/time. That may help narrow down if a rule is making this change, and which one is doing it.

Thanks for clarifying, as it appears you are instead using this addon: https://marketplace.atlassian.com/apps/27447/table-filter-and-charts-for-confluence?hosting=cloud&tab=overview And...if you are directly copying and pasting from the sprint report then the source of the missing asterisk indicator may be before that…

Adding to Danut's answer... @Mirmelshtein_ Roi -- It now seems that you are asking for the % Completed for different sprints over time, and not for just one sprint. If that is correct, another gadget in the same addon Danut describes does that: the Team Velocity Gadget. With that, you may select to show just the %…

I do not believe the dynamically generated fields show in the issue search JSON (from the REST API), even though they may be accessible to the issue. Perhaps try a quick test and just write it to the audit log to learn if that is the case.

A possible work-around might be...dynamic fields (without a custom field) can sometimes be saved in a created variable (or other field) and then used in the rule. So try this, triggering the rule from an issue which has that field: * trigger: manual * action: create variable* name: varSecurity * value: {{issue.Security}} *…

Thanks for that information. From your notes, it appears you are using this marketplace addon: https://marketplace.atlassian.com/apps/1219300/sql-powered-table-transformer?hosting=server&tab=overview I have not used that one, and could not determine from their documentation how the scope change indicator is added for the…

In my experience, there are different definitions for the concept of a "spike", so how you handle these depends on your team's understanding. A simple definition is "a task included in an iteration plan that is being undertaken specifically to gain knowledge or answer a question" (from Agile Estimating and Planning by Mike…

Thanks! Does your scheduled trigger have JQL to access any issues from which to copy into the new Task?

Hi @claire.maillard There is a suggestion to make this more configurable (or back the way it was before the new issue view). You may watch/vote for that here: https://jira.atlassian.com/browse/JRACLOUD-70098 One possible work-around would be to copy the values to fields (with an automation rule) that could be pinned to the…

Hi @Jeevabharathi -- Welcome to the Atlassian Community! From how you describe your team's process, the burndown chart is correct. The team is releasing to production in a batch, your definition of done appears to include releasing to production, and so the burndown matches that. The built-in cumulative flow diagram may…

Hi @janez_m Just to confirm the symptom you are describing: are you running a scheduled rule, hard-coding the values of 2 custom fields, and the result is the values are not stored as expected from the hard-coded values? In this case, I hypothesize that you have a timing and/or multiple-edit situation for the issues,…

Hi @Kavishika Kahandawala -- Welcome to the Atlassian Community! Which spiral methodology or framework are you using, as there are several? When the way you work has iterations (such as sprints), the Scrum template for a project board may help. The iterations can be a repeated length (e.g., every 2 weeks) or adjusted based…

Hi @凌宝万 Vant Ling (ENG - QA - CN) If you only want to track additions to the sprint, you may see that on the Sprint Report. If you also want to query that later with JQL, such as by adding a label for scope change, you could use an automation rule like this: * trigger: field value changes for Sprint * condition: JQL…