Bill Sheboy Expert

I am glad it is working now. FYI that "next-gen" projects are now called "team-managed" and the "classic" ones are "company-managed". I try searching for both old/new names when looking for posts, defects, etc. to find answers. Thanks!

Using your JQL and the Lookup Issues action, you would create a list of issue keys, and those would be the input to the advanced branch to then link to the triggerIssue or the created daily task. {{lookupIssues.key}}

Thanks, and another way to do this is triggered on issue transition (rather than scheduled). For example to move TO blocked: * trigger: issue transitioned TO one of your blocking conditions * condition: issue type is whatever you use a children of epics * branch: on epic parent* condition: epic is not currently in blocked…

Acceptance Criteria sounds like a custom field your admin added (or from an addon tool). What type of field is Acceptance Criteria, and when you edit the field in issue view do the colors you set display correctly?

Hi, Kyle. You found the correct page with examples for the JSON edit of that field. The tricky part is often confirming the name of the smart values (spacing and case-sensitivity), and this how-to can help with that: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ For story point…

Hi @Sravan Duddella Are you using an Automation for Jira rule to do this? If so, would you please post images of your rule for context? Thanks! Without seeing your rule, I expect you can trigger the second case on an issue transition, check if the parent Epic is "blocked" with a condition, and use a second condition to…

Hi @Kyle Chalmers -- Welcome to the Atlassian Community! You appear to be using a team-managed project. Is that correct? If so, customizing the displayed fields on boards/backlogs is not yet possible. You may watch/vote for this suggestion to add that feature: https://jira.atlassian.com/browse/JSWCLOUD-17336 Kind regards,…

Hi @Luis Díaz -- Welcome to the Atlassian Community! I do not believe those attributes of a Sprint are available for JQL filter usage. For the attribute you noted, sprint.state, that can instead be filtered using the functions openSprints(), closedSprints() and futureSprints():…

Hi @Hollee -- Welcome to the Atlassian Community! Which field are you showing in the backlog that has the font with the color? I just tried this with the Description field on a company-managed project and was able to see the font color in the backlog view. Kind regards, Bill

I believe this is the incident for this symptom on the status dashboard, which you may subscribe to and see progress: https://jira-product-discovery.status.atlassian.com/incidents/s46gs94w58v9

Hi @Puneeth BS -- Welcome to the Atlassian Community! As you note, you could do this with a custom field and Automation for Jira rule. To get you started on creating your rule, please review this documentation and examples: * https://www.atlassian.com/software/jira/guides/expand-jira/automation *…

Hi @Mauricio Cordeiro -- Welcome to the Atlassian Community! First thing: what problem are you trying to solve by doing this? I ask that question as if your "daily task" could return the same list of issues, day by day, the list of links could get longer and longer. Next, you could try using advanced branching on the…

Hi @John Warnas Adding to the answer from @Fabio Racobaldo _Catworkx_ ... Here is the suggestion to add this feature to team-managed projects, which you may watch/vote for to see progress: https://jira.atlassian.com/browse/JSWCLOUD-20809 Kind regards, Bill

Hi @Abhinay G -- Welcome to the Atlassian Community! One way to do that would be with an Automation for Jira rule. Please look here for information and examples to get you started: * https://www.atlassian.com/software/jira/guides/expand-jira/automation *…

Hi @Dheemanth Uppalapati -- Welcome to the Atlassian Community! What problem are you trying to solve by doing that? Knowing that may help the community to offer you suggestions. Without knowing that...I suspect there is a REST API to create such folders, and that could be called from an Automation for Jira rule using a web…

I found this suggestion for this same symptom logged yesterday, so others are seeing this also: https://jira.atlassian.com/browse/JRACLOUD-79129

Hi @Rajesh Konda Just following up to ask if this is a team-managed project. If so, it appears that only project-admin (or higher) permissions can remove the watcher at this time: https://jira.atlassian.com/browse/JSWCLOUD-18480 I did not notice this in my test as my permissions were site admin. If you have at least…

Hi @[deleted] -- Welcome to the Atlassian Community! One way to solve this with an automation rule is to add a custom user field which saves the assigned person when the issue was in progress, such as "Assigned Developer". That field may then be used later to re-assign the issue when rework is needed. One advantage of this…

Hi @Taylor purcell -- Welcome to the Atlassian Community! Unless you have a fixed list of keywords or plan to regularly update the JQL, I am unclear how you could do this with out-of-the-box features. * Let's assume you are looking for specific keywords or phrases in the text fields (e.g. summary, description, etc.). You…

Hi @Paty Souza Adding to suggestion from @Mohamed Benziane ...you reminded me that I never followed up answering that other thread. Thanks! Short answer: I believe you can only do this at this time by hard-coding the dates in a series of conditions, and then increment the due date multiple times with re-fetches. Longer…

Hi @ED DevOps D2 My apologies as I just discovered I never answered your follow-up question! My original "short answer" of hard-coding these with repeated conditions, one holiday at a time, appears to be the solution at this point...because... After experimentation I found that smart value, list filtering cannot use…

Hi @Jonathan Santos Your Jira site admin can search the audit log for "project version deleted" to find this information. And, there are most likely version management tools in the Atlassian Marketplace to make seeing the version history easier. Kind regards, Bill

Hi @Alex Shirokov Please take a look at the documentation of the {{changelog}} smart value to learn how to do this: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--changelog-- Also, I recommend reading over the smart values and examples on that page; there is a lot of good information to…

Hi @Angela Jackson -- Welcome to the Atlassian Community! How would you know to which epic to assign the issue (e.g. story)? If you can determine it from fields in the story, and then find the epic with JQL, this could be done using an automation for Jira rule. Please look here for some information/examples if you want to…

If those email addresses (or Jira Users) are in the issue field, an automation rule could parse them to send to all. One thing to watch for is any SLA limits on the number of emails sent/time unit for automation rules (if you are on a free license account). I expect it would also be possible to add 50+ mentions in a…

Hi @Brad Smith Short answer: I do not believe such a report as an automated email is possible with out-of-the-box features. For some work-around ideas to try... * Take a look at the built-in dashboard gadgets to see if something would be close to what you need, and then send out an email with a dashboard link * Build a…

Hi @Asparuh Georgiev What is the type of that custom field? I believe some of them, like Label, have always been case-sensitive. Kind regards, Bill

Hi @Cami Lawson I believe the only way to do that currently is by changing your language/region to one that does not use numeric separators. There is a suggestion to make this configurable (independent of language), which you may watch/vote for to see progress: https://jira.atlassian.com/browse/JRACLOUD-75109 Kind regards,…

Hi @Ron Aisen -- Welcome to the Atlassian Community! First thing: I am not using Insight and so my suggestion is based on what I understand about automation rules...not Insight's IQL. If you can create a JQL/IQL statement to find the objects, perhaps try using a Scheduled Trigger on the…

Hi @JG Meillaud _ What problem are you trying to solve? Knowing that may help the community to offer suggestions. Until we know that... What you ask cannot be done directly from JQL. Instead you could: * Create and save your JQL as a filter, and ask the users to subscribe to the filter * If the users are associated to…