Bill Sheboy Expert

Hi @Mateus Almeida I wonder if you are running into one or more collisions, possibly due to... a) In one of your rules, you appear to be trying to add the assignee three times, with three different smart value expressions: {{assignee}} {{issue.fields.assignee}} {{assignee.key}} Have you tried removing two of those (leaving…

Hi @ravi teja -- Welcome to the Atlassian Community! First thing, I have not tried doing what you ask, and... There appear to be several REST API methods (marked as experimental by Atlassian), to manage custom field…

Hi @Andi Klaeusli -- Welcome to the Atlassian Community! @Trudy P Claspill helped you with the branch part of your rule, and I wanted to ask about your overall scenario... You describe: * there is an epic, * with multiple recently created stories, and * for which there is a dependency ordering among the stories, * which…

Hi @Ben Glasthal First thing, there is nothing out-of-the-box which can do that. Next, I respectfully suggest having a chat with leadership about how they want to use that information...what problem are they trying to solve. I wonder how a single number for resolution time (with no other information) would help a team.…

The alternative is what I described earlier...So one rule would be: * trigger: version released * action: use that version's name to create a new one with the higher number And the second rule could be: * trigger: sprint started * branch: on issues in the sprint* condition: fixVersion is empty * action: edit issue to…

The {{version}} smart value is only available with the version-related triggers, and so your rule cannot use it when triggered on Sprint Started. Please note the difference as that smart value is singular, as compared to the issue-related smart values of {{issue.fixVersions}} and {{issue.versions}} (which is really the…

That might indicate the issue is configured to become read-only after moving it to closed. I believe that would require a Jira admin to configure that behavior, so perhaps check with your admin to learn if that is the case.

Hi @Antonio Carvetta -- Welcome to the Atlassian Community! Would you please post images of your complete rule and the audit log details showing the execution? Those will provide context for the community to offer ideas to help. Thanks! Until we see those... What you describe is a fairly common use case, although you do…

Thanks for that information, @Faith Barnett Would you please post an image of your entire rule? The audit log seems to show there are at least two create issue actions, and one of them is failing. Seeing the entire rule may provide context for this symptom.

Have you tried to use the Lookup Issues action that I suggested? Have you tried to reference the lookup results in the Slack message? With those, you can find and list the items which are in the release. That can be provided in a Slack message, email, etc.

Thanks for that information, and just to confirm: * Your automation rule does not appear to add any comments to the newly created issues * After the issues are created, some of the features of comments (and comment saving) does not work for the newly created issues If those are correct, I do not know what could cause those…

First thing: when posting images of your automation rules, please post the image of the entire rule. This can be done using a screen capture tool, such as one that can scroll the browser tab. When you post multiple images for pieces of a rule it can be difficult to see the overall context. Next, also post the image of the…

First thing: please try to stick to one conversation thread when responding. Otherwise it becomes difficult to follow and readers often understanding that each thread is a solution approach to try. Thank you. You note that you tried the math operation syntax and that did not work. Please post images of your current rule,…

Thanks, @Nicolas Philip When I originally tested lookup tables, using a created variable as a parameter in a table.get() it did not work, and it rechecked and it does work now. What is the specific variable name you are using for the created variable? And...if "is this real?" is in fact your issue field name, I wonder if…

Thanks for that information. A couple of things to check: * Ask your manager (who can see the board) to examine the filter for the board, and to check the shares/permissions for it. * Ask your site admin to "view all boards" and check if the location of the board was changed somehow during the edits.

Hi @Mimi Peters For a company-managed project, I am certain you could add a label based on the reporter. Depending on the triggering event, you might be able to do this with other Jira features or marketplace addon apps. My question would be: what problem are you trying to solve by doing this? I hypothesize you are doing…

Hi @Boleslaw Nowak What have you tried thus far to solve this? If you have a rule started, please post images of the complete rule and audit log details showing the rule execution, and described what is not working as you expect. Those will provide context for the community to offer suggestions. If you have not started a…

Hi @michelle.purcell The branch you are using is assuming the trigger issue is an epic. That does not seem to be what you want, correct? Instead you want a rule which can handle the different issue types. Perhaps more like this: * trigger: issue created * action: re-fetch issue (It is a good idea to add this when using the…

Hi @Santiago_Perez Eventually, an epic's visibility will be controlled by the issue status (an not the epic status as the field is going away). Until then it can be easy to forget to change the epic status...and so you could add an automation rule to do this for you: * trigger: issue transitioned to Done * condition: issue…

Hi @Jory Howell -- Welcome to the Atlassian Community! When you created the board, did you set the location to a project or to your profile? And when the board was moved/handed off, did you change the location to your manager's profile or somewhere else? Kind regards, Bill

Hi @Kunal -- Welcome to the Atlassian Community! The release is used by the issues, and so it does not contain the list of them. To create your release message, try using the Lookup Issues action, with JQL to get the issues, and then you can reference them in the email (as shown in the…

Please try to keep your responses to one thread in the question. That will help others see if there are multiple suggested solutions. Thanks! When you look at the history for that issue, what do you see regarding the Due Date? Was it updated each time you changed it, and if so, who does it show changing the value? And, is…

Hi @Nicolas Philip Would you please clarify what you meant by this: Also, it might worth clarifying in your documentation that the returned values are strings only and one can use the asNumber function to convert the values as numbers if needed. My testing indicated that lookup table values contain objects, and so entire…

Hi @UdayKiran I wonder if something in the combine/merge of the values from the cells is changing the result, such as collapsing the double quotation marks. You could check that by referencing your cell H34 in another cell with =H34 and see what it looks like. Have you tried to in-line to concatenation of the text, like…

Hi @Matthew Pavouris -- Welcome to the Atlassian Community! Without seeing what your rule is writing into the comment, it is difficult to guess what is happening. Please post images of: * your complete rule, including details showing the comment add action, * of the audit log details showing a rule execution which added…

Hi @raghuvarmaofficial My understanding is the branch type Destination Issue only works when the trigger is Issue Linked, not when a link is removed. Instead consider changing your branch to only the currently linked issues; that is, the ones which remain after the link is deleted. Kind regards, Bill

Hi @Patricia Johansson One way to do this would be to call the REST API to get all the components for the project, and then iterate over them (or build a single search expression with reg ex), search for them in the description, and add the components that you find (using a JSON advanced edit). I haven't tried this…

Hi @Elif Alverson What do you mean by during the issue creation? For example... * Are you manually creating the issue and want the UX to consume the document from a location/link provided, adding it as an attachment * Are you importing issues and want an import field to reference the document location, and then add it *…

Hi @John Colosi First, I want to note that is a clever work-around for no Create Variable action in the Server/Data Center version of automation rules. Other approaches would be to store your search expression for the replaceAll() call in an entity property (or custom field), re-fetch, and then use that directly. That…

Hi @John Colosi Have you tried to use split() on the newlines (effectively removing them) and then join() with the character of your choice to concatenate the text? Depending on the source text, you may want to check for both newline and line feeds. Kind regards, Bill