Bill Sheboy Expert

Hi @Danielle Cantrell There are a couple of open suggestions to add this idea, which you may view and vote for: Choose whether or not to hide empty custom fields from issue views https://jira.atlassian.com/browse/JRACLOUD-2997 Option to show or hide empty Epic name and Sprints fields at the issue view screen.…

Hi @Rajesh Konda Let's diagnose this in two steps: First, test the JQL to confirm it is returning what you expect. If not, make adjustments until it does. Next, if the automation rule is still not working, please post an image of the rule and the audit log so we can see what is happening. Best regards, Bill

Thanks for the update. If this approach works for you, please consider posting back here to share your findings and mark this question as answered. That will help others find solutions faster in the future.

Hi @Taranjeet Singh I'm using it in Cloud right now, and it is listed on the documentation page: https://support.atlassian.com/jira-software-cloud/docs/automation-actions/ It is not listed on the server version documentation, so maybe it is not in there yet: https://confluence.atlassian.com/automation/actions-993924834.html

Hi @Casey_Jones -- Welcome to the Atlassian Community! If I understand you correctly, the workflow of your use case is: * When an issue moves to Done * And the issue is a sub-task * Get the parent info (maybe with the temp variable feature) * For the sibling sub-tasks* Are they all done?* If so, make the parent's migration…

Hi @Rajesh Konda You are asking about automatic notification of high priority issues that have not been updated for 45 minutes in JIRA cloud, and not in JIRA Service Desk. Is that correct? You could solve this in two ways: filter subscription and automation rules. * Filter subscription is the easiest way to do this…

Hey @krnaicker -- Welcome to the Atlassian Community! After a bunch of tinkering, I finally got this to work in an automation rule: {{issue.properties."myNameSpaceExample.myKey"}} The values I used when I Set Entity Property were: * Entity Type: Issue * Property Key: myNameSpaceExample.myKey This didn't match any of the…

Leon, I am glad that worked for you!

Hello, and thanks for this information @Cristiano This feature will help solve problems that could have only been solved previously by adding custom fields or logging working comments as temporary storage. Any thoughts to strongly typing these variables, such as date/time, number, list, etc.? Best regards, Bill

Hi @Steven Mason -- Welcome to the Atlassian Community! Without buying a marketplace add-on for audit functions, the only other ways I know to do this are to create a webhook to push the log events, or to create a bunch of automation rules based upon different triggers. The webhook method can expose changes which don't…

Hi @Leon -- Welcome to the Atlassian Community! I recall seeing another post suggesting setting to the minimum date value, or null, to clear a date/time field with JSON. Have you tried either of those? Best regards, Bill

Hi @Saifeldin Ibrahim -- Welcome to the Atlassian Community! I do not believe that there is a built-in way to do this, such as with JQL. You could try the following to help solve this. These solutions vary depending upon how often you need this information and if you want to spend more money on products. * Export the data…

Hi @Ian Balas As an alternative, have you considered using automation rules to create the sub-tasks? That could be triggered off the original issue create or edit. Please look here for information to get started with the automation rules:…

Hi @Anupama Belakhindi -- Welcome to the Atlassian Community! I do not believe you can use status category with many of the built-in gadgets. As a work-around, you could add a custom field to have the same value, and report on that. * Add a custom field * In the workflow transitions (or with automation rules) set the value…

Hi @Brandon There is also a suggestion to add the ability to order the linked issues, such as by status or a custom field. Here is the item if you want to review/vote for it: Ability to order the linked Issues https://jira.atlassian.com/browse/JRACLOUD-68543 Best regards, Bill

Hi @Mano I do not believe there is anything in out-of-the-box JIRA to do that. Perhaps you could check the marketplace to see if there is an add-on product you could purchase for that: https://marketplace.atlassian.com/ Best regards, Bill

Hi @fiona_lebel I just tried a REST API call with an issue search for JQL and it worked for me. And, checking the Atlassian status page, I see no open incidents: https://developer.status.atlassian.com/ If you post your REST API call, perhaps the community can give you some ideas to try. Thanks, and best regards, Bill

Hi @Regli Núñez I am curious...what was the issue that caused the problem? Best regards, Bill

Hi, Milica. If this ends up helping you, please consider marking this question as answered. That will help others in the community find solutions faster. Thanks!

Hi @Slick Rick I believe CHANGED has a modifier of DURING (startDate, endDate) to allow comparisons within a time-frame. And, as you noted earlier, this will help for things like status but not allow seeing all field at a point in time.

Hi @Ted Patterson This is not possible yet in JIRA Cloud. There is an old suggestion to add that feature, and you may review/vote for it here: https://jira.atlassian.com/browse/JRACLOUD-61395 Best regards, Bill

Hi @Petter Gonçalves The feature suggestions you noted are both 7+ years old. What is the likelihood of such things moving forward due to votes from the community? Thanks, and best regards, Bill

Hi @Alex Hadden-Boyd It does not appear that is possible yet. I found the suggestion below for the server version, and I pinged to learn if there is an equivalent one for the cloud version. You can create a suggestion if you cannot find one, adding your own supporting details.…

Hi @Rafat Sarosh Your posting is to a community forum, and not production support. If you indeed have an urgent production support issue, please contact Atlassian support directly to submit a ticket: https://support.atlassian.com/contact/#/ Otherwise, if you are asking for help from the community you will need to provide…

Hi @Jim Gentile -- Welcome to the Atlassian Community! You seem to be asking more of a process question than a JIRA tooling one. JIRA is just a tool to help manage a team's work. The team you describe is using high-level, status values (e.g. In Progress) while the majority of process details are in the sub-tasks. All of…

Hi @Milica Djuricic You are using this "Cumulative Flow Diagram" (CFD) report correctly. The design in JIRA just limits what you can see. This is the Next-Gen version of this report. The Classic project version of this report has the Refine Report option, but Next-Gen does not. What a CFD can show is: * Arrival rate of…

Hi @Kristaps Lizanders -- Welcome to the Atlassian Community! I have not personally seen this issue... Looking at some other community postings, Atlassian support suggested to other people to first change your time zone under personal settings and then try to change the language. Best regards, Bill

Hi @Daniel Mak -- Welcome to the Atlassian Community! I suspect you are running into the same limit as the REST API, and you would need to use the maxResults and startAt parameters to page for more than 100 records. Also remember to specifically use and ORDER BY statement so the pagination works in a predicable manner.…

Hi @Dionei Piazza You cannot use the JIRA Kanban boards to do as you ask because of the built-in assumptions that the first column=Not Started and the last column=Completed. So mapping the status values would create issues for any other epic workflow you have in mind. If you just need a visibility board (no moving items),…

Hi @Rhea Mehta If you just need to see the count of days in status on the board, for Classic boards there is a setting to do this: Board settings > Card Layout > Days in Column This will start showing dots on the cards, beginning with 1 day, and adding more dots and changing the colors over time. You can hover over the…