Mykenna Cepek Expert

Configuring the Edit Issue action like this should do what you need:

I'm noticing a few problems in the rule you posted on 6-Mar-2022. * Early in the rule, you should probably use a conditional to check the Issue Type. You can only create Subtasks on standard issue types (e.g. Story, Task, etc). Based on the trigger, this rule will run whenever any issue of ANY type is created in the…

I get it, @Salvador Martin. I'm not going to be an apologist for Atlassian, as I've been pretty outspoken about certain areas of their product line myself (e.g. Automation). However, let's remember that Confluence is a "mature" product, which has advantages and disadvantages. I suspect that most of the problems you outline…

In response to a hack that I offered above, @Colum McAndrew wrote (and @Denise M Parmenter liked): I'd be interested to know more about your "weekly reminder of blockers" automation. We want to flag tickets in a status that have been in that status for a particular period of time, and your solution sounds like the answer…

There may be a better solution, but I'll suggest an approach I'd use to solve this. I see you're using Jira Server, which I don't have access to. I'll show my work here for a Jira Cloud solution, and you can replicate the effort to find what works for you. I'd start by investigating the URLs that Jira uses to display the…

And if the Oxford Comma (or not) isn't pedantic enough for you, wait until you find yourself spending time adding a conditional to pluralize a word when the count is not equal to "1"!

In my former career as a software developer, I learned this too. Users often want to suggest a specific implementation of some new functionality. Even product architects and leads can fall into this trap. I learned to find ways to ask "What's the intention?" or "Help me understand the broader need for this change" --…

See the docs here for examples.

Try this: {{#issue.affectedServices}} {{#last}}and {{/}}{{name}}{{^last}}, {{/}}{{/}} Omitting the final comma (before the 'and') is not easy, and arguably not desired (Oxford comma).

I've had difficulty with rules that try to access issues outside the Projects configured for that rule. I answered a different Community question recently where I tested just that. The rule didn't work until the Scope/Projects under "Rule details" included Projects for all issues of interest. "All projects" (global) scope…

@Marcus Chuah: ensure that the project which contains the Epic is configured for the rule.

Thanks to each of your for your contributions! Your help supporting others is really appreciated, particularly among the Community Leaders shouldering a lot of the load. I'll call out @Stefan Salzl for diagnosing an Automation configuration this week that I missed the first time on a user question. You, sir, ROCK!

Hi @Ramiro Justet. To clarify, my comment was addressing the original question "How do you manage the time tracking inside of Jira?". Tempo Timesheets focuses on the logged time (aka "Time Spent", a total of the "Worklog Entries"). The "Original Estimate" and "Time Remaining" values in Jira have value for reports and work…

Nice catch, @Stefan Salzl. Almost certainly the "Run a JQL search and execute actions for each issue in the query" option is erroneously checked.

That's why I originally suggested you "post a screenshot showing the configuration of your 'Edit Issue' action." I'm glad you were able to figure it out.

Review the answer I offered in this thread on 30-Dec-2021. Lots of good information there.

Great overview for how Atlassian's core products can help organizations align more completely!

Start with these: * Best practices for optimizing automation rules * 7 Things You need to Know about Automation for Jira Anyone else have links to docs that are still available online?

Ok. What does your Audit Log for this rule show? Can you screenshot both the overview (all recent runs and changes for this rule) as well as the details for the latest execution?

Your screenshot ends after the third "And create variable" component. So we can't see what your rule looks in the vicinity of the "Create issue" component. Please post a screenshot of the bottom half of your rule (so we can see ALL the rule components). 

The rule needs to be enabled in order to run. There's a little switch that shows green in the top-right corner when a rule is enabled (when viewing the Rule Details). The rule also has to be configured for the Jira Project(s) where these Epics and Story-level issues are located. You should also look in the Audit Log to see…

The "Log Action" is really helpful in situations like this. Before the "Send Email" action, add an "Log Action" which outputs something like the following (for your particular situation) into the Audit Log before the rule tries to send the email: Email addr = "{{issue.Email Address[Short text]}}" This will clarify exactly…

Take a closer look at the documentation on using Smart Values: * Smart Values Overview * Math Expressions with Smart Values

@perza - Your question (and the discussion that it warrants) really belongs as its own question (rather than in the comments to this article). Please post your question as a new question here (click on "Ask the community > Ask a question" in the top-right). Ideally, include the specific fields you are looking for (and…

Here's another one: Tempo makes my heart beat faster!

The Atlassian Community is a great place for some of these questions. @Philippa Ford: when searching for issues with JQL, sprint names aren't available for fine-grained searching. So you cannot say something like: AND sprint !~ "grooming" In JQL sprints are identified by their internal ID (a number). You can see this when…

I think that issue-level archiving is supported by Jira Data Center and Server only (and in JSM). I believe issue-level archiving is not available for Jira Cloud (in case anyone finding this thread was wondering). Jira projects can be archived (View All Project > 3-dots menu for a specific project > Archive).

Since your original question was "Is the condition correct?", and I believe I answered it, would you be willing to accept my answer? That's important feedback, especially for Community Leaders. Thanks!

The technique I illustrated recently to answer this other question... https://community.atlassian.com/t5/Automation-questions/Adding-watcher-to-subtasks/qaq-p/1939011 ...might work in your case also.

@Tempo Support confirmed what I outlined in my answer here: * Jira internals force Tempo to show logged time under the "All" tab. On the positive side, you can't see who logged time, but you can see that time was logged. * As for this seeming to violate the Tempo permissions granted for the user who should not be able to…