Bill Sheboy Expert

Hi Greg, Would you please post an image of your complete rule? That may provide more context for what is up. Regarding server versus cloud, there are definite differences in automation. For example, {{#issues}} only works in server for iterating over the result set from a JQL. Cloud needs to use branches or lookupIssues to…

Hi @Viktoria Lukinova -- Welcome to the Atlassian Community! For an agile team I am puzzled why there would assigned tasks with "deadlines". I could understand "want dates"... regardless of that... You could put together the suggestions from @John Funk and @Walter Buggenhout to either build a dashboard or add quick filters…

Hi @Colin Sauvanet I tried to create a version (Classic Board) using the same steps and it worked for me with that same date format. And, I saw some older resolved defects in the public backlog for this symptom fixed about 5 years ago. I suggest asking your site admin to check your settings: * Administration > System >…

Hi @[deleted] -- Welcome to the Atlassian Community! I believe that you cannot show that dynamically rolled-up date with a JQL filter with out-of-the-box Jira. If you have a scripting add-on from the marketplace, you could recreate the roll-up field. Or, you could use a custom field and automation rules to roll-up the…

Hi @Colin Sauvanet When you use the calendar picker to select the date, what format does it enter in the field? Best regards, Bill

Hi @Rafal Sojka Adding on to what @Haddon Fisher suggested... One consideration is do you need the task and sub-task values to remain in synch, or can the sub-task value change to be different later. If it can change, consider using an automation rule to copy the value and so it will remain independent for edits. Best…

Indeed, confusing. I wonder if this behavior is a Classic / Next Gen issue (where many names appear overloaded) or a hold-over of allowing users to enter a value case-sensitive and then matching internally on a value which is case-insensitive. Certainly this bothers the DBA/DBE folks trying to use JQL ;^) __Bill

Hi @Pathan Zubair Khan Are you noting that you were not aware of the automation functions, or that you cannot find them? For a Classic Project, you may find automation rules with: * Project Settings > Automation For a NextGen project, you may find them with: * Select the lightning bolt icon (automation) > Manage Automation…

Hi @Manny Ju -- Welcome to the Atlassian Community! No, not yet. There is a suggestion to add that feature, which you may view and vote for here: https://jira.atlassian.com/browse/JSWCLOUD-17631 Only a few built-in fields support required at this time, using a validator on a project's workflow. Best regards, Bill

Hi @Siree Yes, you may do that with a global / multiple project rule. For example, let say when a version is created on Project A that you want to also create it in Project B, you would use: * Create a global rule in Project A, selecting Projects A and B as included * Trigger: Version created * Action: Create version* Copy…

Hi @Gui Ávila Have you tried something like this: project = myProject AND (issueLinkType NOT IN (Blocks) OR issueLinkType IS EMPTY) ORDER BY Key Best regards, Bill

Hi @oliver.lin -- Welcome to the Atlassian Community! Have you solve this issue already? If not, please consider using an example story/issue and calling the REST API manually to confirm the name of the field. Then you may update your mapping. Here is the documentation for how to do this:…

Hi @TJ -- Welcome to the Atlassian Community! If this was working in the earlier server version for you, I suggest you ask your site admin to submit a support ticket to Atlassian: https://support.atlassian.com/contact/#/ Best regards, Bill

Hi @Krithica G If the "hold time" is also in minutes, why couldn't you just subtract that time also? And perhaps, persist it in a custom field and update it so it is available for the subtraction. Please note that by subtracting the value of "hold time", the result is no longer "time to resolution". It would appear to be…

Hi @Daniel Tranca I wonder if this symptom is a field configuration or permissions difference between the two projects. Please review the fields first, as that error seems to indicate a custom field from the source project may not be configured for the destination project. Best regards, Bill

Hi @Rajesh Kumar Sahoo -- Welcome to the Atlassian Community! It is not yet possible to manage automation rules with built-in functions. There is a suggestion in the Code Barrel backlog to add this feature: https://codebarrel.atlassian.net/browse/AUT-999 Best regards, Bill

Hi @lisa I believe that you cannot drag-and-drop to change the ranking or parents of initiatives on the roadmap. Instead this is shown based upon your sorting order. Please see this documentation for more information: https://confluence.atlassian.com/advancedroadmapscloud/sorting-issues-1019379755.html Best regards, Bill

Hi @Pathan Zubair Khan Have you considered using the built-in automation rules instead to make this change for the text field? Here is a documentation link if you want to consider it: https://support.atlassian.com/jira-software-cloud/docs/automate-your-jira-cloud-processes-and-workflows/ Best regards, Bill

Yes, that appears to be the issue. The gray line is flat on the x-axis because there were no issues in the sprint at the start, so the trend never starts above zero. This is the intended behavior, as opposed to other burn-chart designs which reset the trend line if the scope changes. __Bill

Hello @Marcelo Piveta -- Welcome to the Atlassian Community! Would you please post images of your burndown and burnup charts? Often a cause of no trend line is starting the sprint before any issues have been added. Is that the case? Best regards, Bill

Hi @Jack Garrod Have you tried {{fieldChange.field}} as that seems to work for me to give the name. And...after the "new view" goes into effect, it'll only ever be one field at a time per edit by user (right?) so no need to worry about only the first change being captured in fieldChange, which is what happens today. Best…

Hi @Nilupa Rupasinghe That is interesting... That version of the call usually includes the specific board id, as in: jira1.com/rest/agile/latest/board/123 https://developer.atlassian.com/cloud/jira/software/rest/intro/#introduction If you include the board ID do you see a difference for the different instances? If so and…

Hi @Leah Barthelme and @Jack Brickey For your desired outcome, Jack's suggestion works well when you know that the start date and due dates of the child issues (stories) are accurate. One way to help would be to use another automation rule to set a story's start date when it transitions into an "in progress" status. Due…

Hi Neha, The automation for Jira in Cloud is built-in, so you should be able to check if the test execution information is available without any additional add-ons. If you cannot easily identify the names of the smart values (fields) for the data, you can make a test call to the REST API with a user story that has Zephyr…

Hi @david_nikulin I did not see any answers to this question in the community forum. Have you considered submitting this question to Easy Agile Programs support for an answer: https://marketplace.atlassian.com/apps/1219491/easy-agile-programs-for-jira?hosting=cloud&tab=support Best regards, Bill

@Rabbit Stoddard if you post your current rule maybe the community will see something to help. __Bill

Thanks for that information, @Claire Dufetrelle Regarding disabling delete permission, some customers find it useful to add a custom boolean field, such as Abandoned. You may mark an item as Abandoned when it would have been deleted otherwise. Updating your reports and board filters to remove Abandoned issues hides them.…

Hi Craig, I am unclear what you are asking. Perhaps you could give us some specific example issues for the two boards, and what makes them different. That will help you figure out the filters to display them on the boards. And, here is the documentation on configuring Classic boards to provide a reference:…

Hi @Marcelo Montaño Sánchez When you note "current user", who do you mean? For rules triggered on automation action, I believe the actor is the automation user. For manually triggered rules, you can get that person with {{initiator.displayName}} Best regards, Bill

Hi @Jasmin Müller Have you already resolved this? If not, the only way I found to remove things from list fields (e.g. Component, Labels, Version, Links) is to treat them like strings, and... * join to convert to a delimited string, such as CSV * use string functions and RegEx to remove the target value(s) * as needed,…