Derek Fields _RightStar_ Community Champion

@gyorgy.rauf Thanks for reaching out. I was ultimately able to get this working. I appreciate you jumping in after all this time to help.

@Kris Dewachter - Thanks for the suggestion. That very well may work - I wasn't thinking in terms of AQL branch setting the {{object}} smart value. That should get me where I want to go.

@Kris Dewachter - Just a note that in order to make the summation work, I needed to join and split the Amounts in the list, like this: {{lookupObjects.Amount.join(":").split(":").sum}} I provide that in case you ever need to do something similar. Apparently, just using "sum" on the list doesn't work for reasons that I…

@Margaret McKnight - I am not going to be able to be of a lot of help. What you have indicated in your note is quite complex with a lot of different variables that need to be fleshed out before I could recommend a specific approach. This is what my company, RightStar, does every day; we work with Jira users like yourself…

I will try that - thanks for the suggestion.

Here is a partial screen shot. I am using the "Create Object" action to create an Assets object. If one of these fields from the issue is empty, A4J throws an error message. The object is created correctly and the rule continues on. However, I get a failure email notification. I tried using an {{if}} conditional, but that…

I hadn't looked closely enough and you are correct - ScriptRunner will let you catch the MentionIssueCommentEvent. This will trigger when someone is @mentioned in the comment (as opposed to being mentioned in the Description or in a custom field. You can get the comment from the event by calling getComment() on the event.…

You may be better off updating the Velocity template than trying to implement this using an external script. I don't recall an "@mention" event that you can intercept, though there may be one deep in the bowels of Jira. There is a MentionEvent that can be raised, but you probably need an app to catch it.

Thanks for jumping in. However, the syntax that you provided isn't legal. You can't embed an AQL within the (). It requires specifying it as an Object Having [in|out]boundReferences. At this point, I think that my only option is to create two Custom Fields. One that limits the selection and one that doesn't limit the…

By the way - this will only notify people of new tickets that were created in the last 2 days and are due in the next 2 days. A ticket that has a longer time span that 4 days will never get notified.

Try this: project = YourProjectName AND created >= -2d AND "Desired Due Date" >= now() AND "Desired Due Date" <= 2d

Do you have an external system where you could create a simple REST API that would return success after a delay? Then you could call that, have the rule wait until it returns, and then continue with the PUT to the database. That would be simple to create if you have an external system where you can run it.

You can't next branches within branches, which is what you are trying to do. You probably need a second rule similar to the first that is also triggered by a change to the Sprint field. Instead of looking for children, you would branch on linked issues. You need to allow this rule to be triggered by another rule (a…

Have you made sure that you are including Released and Archived versions when you view releases?

@Daniel Nalbach Welcome to the community! You cannot edit the default notification templates in the Cloud. What you can do is create an automation to send the email that you want and turn off that notification in the Notification scheme for the project.

I am a +1 on this. I would like to see an editable ROAM field that would show up as part of the Risk summary. This would make it easier to know which risks need to be addressed versus those that are mitigated/resolved/accepted.

All automations that are associated with the trigger will execute. If you don't want all of them to execute, combine them into a single automation with different if/else blocks

If you have Jira Service Management Premium, then you can use the Assets database to create your table. If you don't have JSM, then you can create a new Project with a record for every TO and CC address and do a JQL lookup there to get the values that you need.

When you say that you have "looked through the admin panel," is this the admin in Teams or in Atlas? The message indicates that the Teams admin has disabled the bot.

Go to admin.atllassian.com. If you are an Organization Admin, you can see all of the sites listed on the sidebar of the Products view for your Organization.

Try {{issue.customfield_11992.value.get(0).accountId}}

Try: issuekey in childIssuesOf("XXXX") OR issuekey = "XXXX" That should return both the main issues and all of its children 

Since you have Jira Software, you can use the Epic->Issue->Subtask hierarchy to solve this. Since your "mini-projects" are represented by three different workflows, you would create three new Issue Types. Each Issue Type would represent the type of mini-project and would have its own workflow assigned in the Workflow…

Projects are Kanban or Scrum, their boards are. You can create a new Scrum board associated with the project. This will allow you to have Sprints on that board. 

Have you tried squashing the commits with the wrong issue keys so that they don't show up in the commit history?

The short answer is that you can't move the field. Atlassian has decided for Jira Software, that non-paragrph fields (e.g., Description) belong on the panel on the right. This is a training issue for your users. They will learn where to look for the fields as they become used to the UI.

Use the "join" function of lists. The smart value would look like this: {{issue.Customer(s).join(",")}} See Jira smart values - lists | Cloud automation Cloud | Atlassian Support for more information

No. There are essentially three groupings of fields on the righthand panel: "Details", which are items that are shown regardless of whether they have a value in the field "More Fields", which are fields that hidden unless you expand that section The third are "pinned" fields, which are individual choices for pinning…

I think that what you want is a smart value that will return something like: <a href-"{{issue.url}}">{{issue.summary}}</a> This won't work in a regular text field. Those fields don't render HTML or Wiki Markup. If you want to have the text displayed as a link, you need to use the Paragraph field type. If you do that, then…

To the best of knowledge, Jira doesn't support colorizing fields at all. However, there is a solution offered in this post that uses colored emojis to give some color indication to your field: Solved: Is there a way to configure different colors for v... (atlassian.com)