Bill Sheboy Expert

Hi @Sundy Iyer -- Welcome to the Atlassian Community! Based on what you describe and the JQL you are showing, the issue which is not showing may have been created more than 60 weeks ago. Is that the situation? Kind regards, Bill

Hi @Jaime Laird That should be possible using automation rules, with some things to check first... * Custom fields (like your Roadmap field) are usually supported by automation rules. I suggest trying to create a rule to determine if your field is listed. If you do not see it, the field may still be available as a smart…

Hi RSavage@stellarindustrial.com What have you tried thus far to solve this? I believe you can still add people as watchers or mention them in comments with automation rules for JPD projects, the same as other project types. Kind regards, Bill

As long as there are fewer than 100 issues, you could instead call a function of the REST API, as that will ignore the project-scope limitation. (When there are more than 100 issues, you would need paging and that is challenging to do in a rule.) The function to call…

You can find these if you are a project admin: * looking at your board, find the lightning bolt icon near the top, right side of the page * select that icon, and then audit log * or...select manage automations If you look in the log, you may find recently executed rules to check.

Hi @Ashley Wehmeyer -- Welcome to the Atlassian Community! Please check if you have an automation rule which is assigning the issue, based upon who transitioned it on the board. You can confirm this by looking at the issue history or at the automation audit log. To stop this behavior, try disabling the rule. However...it…

That link is to the instructions for Jira Server / Data Center version. For Jira Cloud, you have a better action of using Lookup Issues. For that, your scheduled trigger has no JQL. Instead use the JQL with the Lookup Issues action: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues

I confirmed your results that the JSON edit with the rule action is using a function which can only add and copy. Here are a couple of other approaches to try: * Delete both links (as you are currently doing), followed by a re-fetch action to reload the issue, and then add back in one link * Use one of the link's id value…

Thanks for that information. Can you also show how you tried to force to your time zone as part converting/copying the field from UTC date/time to just date (jiraDate)? Doing that should have gotten to the correct date before removing the time component.

What is the time zone setting for your personal settings, Jira profile? How does that value compare to where you are located?

Hi @Upesh De Silva -- Welcome to the Atlassian Community! I am not familiar with that field in the built-in Sprint Health Gadget. Perhaps you could clarify the following: What version of Jira are you using: Jira Cloud, or Jira Server / Data Center? What type of project are you using? Have you checked if this is a…

Hi @Paulo Amaral Would you please post an image of your entire rule and of the audit log details showing the rule execution? Those may provide context for what you are observing. Until we see those...the Status Bean is the component and data/information for the Status field. I would not expect to see those values for the…

Hi @Caio.Queiroz Yes, and...to the answer from @Kian Stack Mumo Systems First thing, what problem are you trying to solve by doing this? Knowing that may help the community offer ideas better aligned to helping with that. Back to your question: the answer is "it depends"... * Lookup Issues results are limited to 100…

Marc, would you please post images of your entire rule, including the details of your conditions and the edit action? Thanks!

Yes, this appears to be a branching issue as I described earlier. A scenario like this cannot be done in one rule as the first branch usually will not finish before the second one starts. There are marketplace apps for cloning which could solve this, however you have noted no additional apps can be added. One possible…

I believe this takes us back to your original idea, of deleting just one of the links. I wonder if it would be possible to, after detecting there are duplicate links, use the advanced edit with JSON to remove the link using its id value, rather than the…

I do not have that information as I am just a Jira customer/user. You may want to watch the release posts for upcoming changes, or add a suggestion for the feature.

Hi @Justin Luk -- Welcome to the Atlassian Community! Have you tried using JQL with the Lookup Issues action? The results can be checked with an advanced compare condition to learn if the results are empty (i.e., equal to 0 size): {{lookupIssues.size|0}} Kind regards, Bill

Hi @Pablo Albani Adding to Mark's earlier question: why are you measuring this? That is, what problem are you trying to solve? For example, is this a billing tracking thing, a process improvement thing, something else? If this for tracking back-and-forth in process flow, please instead consider discussing this with the…

Just to clarify, did you find that a project-scope rule could link to an issue in another project using the Link Issue action?

Rules can use a web request action to call REST API functions, such as the ones for Jira. Here is a how-to article walking through that: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828 The specific function you want is to get all versions for your Jira…

How does the second link get added: with an automation rule, manually, or something else? If it is with an automation rule, you could check if the link is already present to avoid adding the duplicate.

Hi @Garth Smitman That built-in gadget cannot do that, because... Components are defined by project and so your different values for "ABC" in Project A and B are indeed different components. The gadget is using the components' id value and not the display name for the grouping items. There may be marketplace addon gadgets…

Hi @Bridge2Lisbon Lda -- Welcome to the Atlassian Community! You posted this question in the Automation for Jira area, and I believe you are asking about Trello. Please try posting the question here instead: https://community.atlassian.com/t5/Trello/ct-p/trello Kind regards, Bill

Hi @Emmanuel Blanco -- Welcome to the Atlassian Community! I do not believe that is possible with the out-of-the-box Timeline (formerly known as Basic Roadmap) feature. The "child" items use the same bar color as the epic parent above them: the Epic Color. Kind regards, Bill

Hi @Lee Segal -- Welcome to the Atlassian Community! Since the changes for GDPR were implemented, scenarios like this are more challenging to implement. Specifically, you have an email address for your on-call person from PageDuty and it is likely your Jira users have a different user name than their email address. So a…

Hi @Brian Noble -- Welcome to the Atlassian Community! To help focus suggestions, what problem are you trying to solve by doing this? That is, "why do this"? Knowing this may help the community to offer better suggestions. And it may help to discuss this with your Jira Site Admin to learn what they suggest. Until we learn…

My understanding is if the attachment is available by a web location or included in the message it will attach. If that does not work, you could make the web request call after the task is created, referencing {{createdIssue.key}} as the target to add the attachment.

For project-scope rules, the only thing you can do with other projects is Create Issue or Clone Issue. All other actions, such as linking, require a global-scope rule. As you are trying to bypass the global-scope, rule execution limits with the REST API, you could try doing the same for the issue linking. Please note, you…

How is the issue linking happening: manually, from another rule, something else? Knowing that may help to isolate the linking.