Bill Sheboy Expert

Hi @frenciszakarukam Would you please post an image of what you are seeing? When I look at issues views (pop-up, side bar, and single issue view) in both Company-managed and Team-managed projects, my description field shows in the default location at the top of the view with comments at the bottom. Has one of your admins…

Hi @Patrick Cartier Assuming you are using the Field Value Changed trigger... Please try using the field changed ones, like this: {{addedFieldChange.values}} Unfortunately the documentation has the casing wrong on many of these smart values, so you may need to experiment if you want to use the other ones.…

Hi @Hannes Obweger - JXL for Jira I am using Jira Cloud, and that worked for me also. But Tatiana appears to be using Jira Server: did you try it with that version? Thanks! Kind regards, Bill

Hi @Mira And here is the very old suggestion (from 2008) to add capabilities like "default assignee field to the reporter", which you may watch/vote for to see progress: https://jira.atlassian.com/browse/JRACLOUD-14897 Kind regards, Bill

Thanks for that information. The Create Page action doesn't "return" anything to reference the page, and there are no branches to "most recently created page" to reference it either. A work-around would be to use the Send Web Request action after your page is added, get the page information, and then use that in your Send…

Hi @CEDRIC DEVAUX Another way to do this is with default values for a field, using the pipe | operator. For example, {{issue.someFieldThatCouldBeEmpty.value|0}} This would substitute in 0 when the field is empty. For your scenario, the lookup tables could contain a value to use when the field(s) are empty, and the lookups…

Hi @Chrystal Yes, and...to Nic's answer: Jira Cloud does this in a few places with JQL, but not consistently everywhere. And...sometimes it removes the parentheses but does not re-order/re-structure the query to match what you planned! One lesson here is to observe what happens and test after entering your JQL. Kind…

Hi @Lars Morten Nygaard I believe one way to do that is to save the desired status value's ID in a created variable, and then use that in the transition. You may enter a smart value in the Transition Issue action... * type in the smart value, such as {{varMyStatusId}} * and the smart value will appear below the field *…

Hi @Lyle de Groot -- Welcome to the Atlassian Community! For a question like this, it is helpful to post images of your complete rule, the relevant action details, and the audit log details showing the rule execution. Those will provide context for the community to offer suggestions. Thanks! How are you trying to create…

Wendy, would you please post an image of your entire rule showing all of the steps? That will provide some context to help explain what you are observing. Thanks!

When teams are using several different tools to manage work, I can definitely see challenges in keeping things aligned. You may want to investigate if making the assignment in one tool can be used to update the other, using Automation for Jira rules...or a marketplace addon / connector.

You have an Else-If after the block testing for epic creation, and so it is adding subtasks for the newly created task. If you do not want those, remove the Else-if and additional subtask creation. And if for the epic you want to create 2 tasks, you just need 2 blocks: one for each task.

I am just a Jira user, and so have no visibility to Atlassian changing the scoping behavior for iterators. Regarding using the index values with the list, first you build the list with an iterator storing in a variable, as you showed for my example. Then match on the value, such as "(blue*)". And finally separate out the…

I have already described the steps a couple of times in my posts. The rule change would be (in italics): * trigger * branch: on linked issue of your needed type* action: transition the issue

Hi @Priya -- Welcome to the Atlassian Community! Automation for Jira rules trigger/run after an event has occurred. They do not run to populate fields on a view / form as the events have not happened yet. (For example, editing issue fields.) If you have a need to dynamically populate fields based upon other fields, you may…

Hi @Neeti G -- Welcome to the Atlassian Community! Did you solve your question yet? If not... You seem to have posted this in the Automation area, but your question appears to be about issue search, such as with View All Issues. When you download issue search results, the currently selected fields on the view are "My…

Hi @Jeff Hooper Although it was possible for a while to create Subtasks under an Epic, that is not a normal practice supported by the out-of-the-box issue hierarchy. Regardless... I wonder if the recent changes to sunset some of the Epic fields (which seems to be completing work) caused an issue for your rule. If you post…

Hi @Petr AST You posted this in a question and seem to be making a statement instead. Did you have a question? You appear to be commenting about the changes to the automation packaging/limits and the behavior of the admin-managed webhooks feature. There is an open request to improve the webhooks JSON body configuration,…

Hi @Jason Barber -- Welcome to the Atlassian Community! Two things to consider when using the match() function in automation rules... First, the documentation describes the "underlying implementation is based on Java's Pattern class and uses Matcher.find() to find matches". However it does not indicate what actually is (or…

Hi @Snehal Singh This seems to be a duplicate of your other question: https://community.atlassian.com/t5/Automation-questions/Automation-Script-status-resulting-in-throttled/qaq-p/2497597 Please consider closing this one as the other has been answered. Thanks! Kind regards, Bill

Hi @Adolfo Casari Just to confirm, is your {{X}} a created variable or an issue field? If it is a created variable, you would need to split it into a list before it can be iterated upon. For the other part of your question, I am assuming you are using a created variable... Created variables are text, and have no object…

Hi @nessie.liu I am assuming the JQL for your Scheduled Trigger is only finding the epics which are not completed. Is that correct? Back to your question... First thing, there is no need for that Re-fetch Issue action so I recommend removing it. That action is needed for two cases: immediately after the Issue Created…

Hi @Ashutosh Bhonsle -- Welcome to the Atlassian Community! In addition to Nic's suggestions... As you noted you are rather new to using Kanban methods, I recommend pausing to learn about it, and perhaps how it compares to applying the Scrum Framework. Perhaps look at online sources and some book reading: * info from…

Hi @Jelena Tatomir First thing, I recommend creating a new question and linking back to this one rather than adding more questions to it. Otherwise only the people following the older posts will see it to provide ideas. Thanks! Next, if you review this thread's content, and how to use an advanced branch to iterate values,…

Hi @Charles Lindsay That value looks correct...as long as you do not have any extra fields named "sprint" in your Jira site. You could write the {{issue.sprint}} to the audit log to observe what the rule is using for that operation. What type type of project is this: company-managed or team-managed? Would you please show…

Hmm...That was my last idea of what could cause this... As you are the site admin for a paid license (Jira Premium) I suggest next submitting a ticket to Atlassian Support here: https://support.atlassian.com/contact/#/ They may notice something we are missing in the rule / site configuration. When you hear back from them,…

Thanks for confirming that. Then your rule is missing a branch to that linked issue in JSM, before the transition action.

Hi @Elliot Jones -- Welcome to the Atlassian Community! Have you looked into using an Automation for Jira rule for this? There are several PR-related triggers and one of them may be what you need to start the rule and transition the issue(s).…

Hi @Manoj Kumar Emmadi For a question like this, please post images of your complete automation rule, images showing the details of the relevant actions, and an image of the audit log details showing the rule execution. Those will provide context for the community to offer suggestions. Kind regards, Bill

Please review the workflow for that issue type and look for any rules on the transition to Done which restrict which users can do so. I suspect there is a restriction on your workflow to limit which users can move the issue to Done. And, I do not believe the Automation for Jira user can be added to that transition rule.…