Bill Sheboy Expert

Hi @Lorelai First thing: what problem are you trying to solve by doing this? Knowing that may help the community to offer other solution approaches. Regarding what you asked...One quite complicated way to try this is with an automation rule, to monitor the audit log. For example: * set up a webhook to push out the audit…

Hi @Don Hames Yes, and...to Alex's answer: As you want to add multiple stories linked to the issue, when setting the epic link within the branch please use {{issue.key}} as that will refer to the epic in the branch. If you instead use {{createdIssue.key}} that will refer to the last issue created, and so the second story…

Yup, and if the rule Trudy provided did not work, I recommend working with your site admin to submit a ticket to Atlassian Support. Perhaps they can see something in the logging that we are missing. https://support.atlassian.com/contact/#/

Without seeing your rule which is creating the "subtasks", there is no way to confirm that the issues are in fact in the order you expect consistently. If we assume the issues are somehow are created in your sequence ordering... For JQL, it could be this, used with the Lookup Issues action, and assuming the trigger issue…

Hi @Marc Kraak Whatever you try, this will not work completely as there are definitely defects in audit logging as it does not always show who performed the action. We tried pushing out logs (with a webhook) to help see things better in a reporting tool and discovered no users for some actions...later confirming with…

Hi @Pawel Halas Jack's will definitely help you add the label...and... Have you considered instead just adding a quick filter to hide older issues? Or, if you consider these issues as perhaps too-old-to-work-on, use a filter to identify them and then abandon them by adding comment and moving to "done" or some other…

Hi @Anders Harder Adding to John's answer... There are at least 2 open suggestions to add configuration to that 14 day timeframe, which you may vote for/watch to see progress: * https://jira.atlassian.com/browse/JSWCLOUD-21257 * https://jira.atlassian.com/browse/JSWCLOUD-21790 Kind regards, Bill

Hi @Alexey Byzov There isn't anything built-in which easily allows seeing the number of hours logged, day by day. Three possible work-arounds are... * Using an automation rule running on a schedule for each open issue, call the REST API method to gather the worklog history, filter that by the current day, sum the results,…

Hi @Stefannie Tan What problem are you trying to solve by doing this? If this is a release management issue, have you tried assigning issues to a release in Jira, and instead referring to the Release page? Or...if your team has one pending release at a time (which is next), you could make not changes other than adding a…

I am glad to learn that helped, and... It seems the feature of detecting multiple field changes as a trigger has been added for Jira Cloud. Previously this was only in Jira Server/Data Center with Cloud only supporting one field at a time :^)

With Jira, a Scrum or Kanban board can show the issues, in columns by their mapped status values. It cannot show a roadmap on the board also.

Hi @Kane_Ansell First, let's try to clarify your scenario as that may help the community to offer suggestions... Epics typically have child issues, of the types Story, Task, or Bug. Are you actually adding Subtasks to Epics or do you mean something else? For now, I will refer to them as "child issues". Next, I am assuming…

Hi @Kazu -- Welcome to the Atlassian Community! If I understand your question, the answer is no: you cannot see both a board and roadmap on the same view with out-of-the-box Jira features. There are marketplace addon gadgets which can display those together on a dashboard, however they probably will not have the same…

Thanks for clarifying, Jack. And if that rule is still having a problem missing the first epic (and so creating the other) then either we are missing something obvious or the rule is "broken" internally. Sometimes rules get broken due to the number of edits, and other mysterious causes. The way to check that is to…

Hi @Angel Ferreira Please try {{issue.issueLinks}} to do that. Perhaps if you explain your use case a bit more the community can provide more suggestions, as I suspect that you may want to send this list in one notification (e.g. email), and so perhaps bulk processing from a branch would…

Hi @Mark Fan -- Welcome to the Atlassian Community! First thing, and in my experience, I find "chapter" and "squad" are not common agile practice terms, and instead are parts of a couple of niche explanations of agile organizations. Perhaps you could clarify what you mean by those terms. For example, is "squad" a delivery…

Hi @Rosario Morgan -- Welcome to the Atlassian Community! Are you using Jira Cloud or Server/Data Center? Which dashboard gadget are you trying to use? And more specifically, do you have any marketplace addon apps for dashboard gadgets? Kind regards, Bill

With the current features of rules, the only work-arounds for the multiple execution I can think of are: * make the rule run on a schedule rather than on field-change; clearly that is not ideal * use a manual trigger for the rule

Hi @jeremyn First thing, there is no feature yet to edit a created variable within an automation rule; you can only recreate it with the same name. Next thing, how fast is "quick succession" for the changes to fields A, B, C? Is this over minutes or seconds as someone is just changing the values, moving between fields? If…

The summary of the epics you are showing are "TEST" and "TEST 2"... Is that what you expected? Your lookup issues JQL is so simple, I am unclear how this cannot work... When you try this, in advanced issue search and not in a rule, what do you observe? project = DDIL AND issueType = Epic AND summary ~ "TEST" And, what is…

I just tried their rule in my test instance, and it did not reset the list. I am using the default install, and am not storing the checklist with the issue data...which appears to be an option with the Pro version. Also, are you using the Free or Pro version of the addon? At this point, I recommend contacting the vendor to…

That part is to conditionally add a comma separator between the entries, leaving it off for the last subtask. If you do not want a separator between the subtasks' summaries you may remove that part, leaving only this, with a single space between entries: {{#issue.subtasks}}{{summary}} {{/}} To learn more about smart value…

Hi, Lorraine! If a field is supported by rules, it most likely is supported by changelog also. I recommend trying your field to see what happens. And...smart values are name, spacing, and case-sensitive, so if you are in doubt of the smart value for your custom field, please use this how-to article to confirm the name and…

Hi @Potip Serhii In the audit log details, to which action in the rule is that error associated? If it is an Issue Create or Edit, perhaps that error could happen when... * team-managed projects are involved and the issue types and custom fields are different * the target project for the issue change does not have the…

Thanks for those screen images! It appears you are using one of the versions of Issue Checklist, and the vendor documentation notes it is possible to clear the checklist items for a company-managed project. Your screen images do not show the lower-left corner of the browser page, so please check if you are using a…

You are probably on Server/Data Center version, correct? If so, the last post from the Atlassian team on this was in August 2021, and still no answer on adding advanced branches to that version for automation…

Hey, @Darryl Lee That's quite clever, and...how many of the fields did you check? I wonder about fields which are either not supported in the REST API or which have some typing issues between get/write motion. I suppose this could be validated by comparing the new issue's JSON with the source (outside a rule or inside).…

Hi @Rohit Kumar -- Welcome to the Atlassian Community! Do you mean you want 10 new tasks, one each assigned to a different user? If so, what is the source of the list of users? Is it a multi-select user field, as with the original question in this thread? Kind regards, Bill

The equals = operator is not supported for the Summary field, and so the contains ~ operator is available. When you test summary ~ "Client for Epic" it will match on any summary which contains at least all of those words. It could contain other words and the ordering is not guaranteed. To test for the exact phrasing,…

I notice that your Lookup Issues JQL does not include a project check. Is it possible there are other issues which have the value in the summary? Just to confirm, can you post the exact JQL you are using for the lookup...not a screen image? And if that is not the problem, I wonder if the JQL contains operator is somehow…