Mykenna Cepek Expert

Those two settings probably are different. My point is that both were disabled, and worklog entries were still visible.

@Andreas Springer _Seibert Group_: Did you see my notes reproducing the visibility of logged work under the "All" tab of an issue, even when Tempo permissions were disabled for the user?

@Dariya Chernologova mentioned the "Tempo Timesheets Access in Global Permissions in Jira". I checked that setting related to my test above. My test user did NOT have that either, and their logged time WAS shown as illustrated above. So I continue to suggest that this is a bug. Logged time is visible, even with all…

Huh. I was able to verify that logged time is visible under the "All" tab on an issue, even if the "View All Worklogs" Tempo permission is not granted to a user: @Hugo Winder: I would recommend that you report this as a bug to Tempo Support, and see what they have to say. It's possible they might not be able to fix it (if…

In my experience, the Tempo "View All Worklogs" permission will control whether I can see all the worklogs for everyone, or just my worklogs. @Hugo Winder Can you share the setting that you are using for that Tempo permission? It's in the Permission Scheme for the Project(s) of interest. For any Groups or Roles listed in…

@Mark Segall indeed it wasn't fair, as I had one coffee plus a half of a Monster energy drink onboard!

I was able to do this in a single rule. The trick is to use one branch to create all the subtasks, and later branch to iterate over the new subtasks. My rule adds the same watcher to all the subtasks, just to show that can be done. @Andreas Wollenhaupt, for your case, you'll want conditionals in the second branch to…

Wow, my first shout-out right in the OP. I'm humbled, @Jenni ! So, one option is to use nested #if statements to suppress an entire section: {{#if(equals(0,0))}} {{#if(equals(1,1))}} hello {{/}} {{/}} But that's starting to get excessive and hard to read. Something else to consider would be to pull out most of the #if…

Ok! So is the rule working for you?

I find this very helpful. It's been a challenge to try to "stay current" across all our Atlassian cloud products in-use. Since it falls on me to highlight new functionality of value to us, and educate users to realize that value, I appreciate the ease of information delivery. Users also get to self-serve, potentially…

See what I wrote yesterday for more steps you need to do.

@Stefan Salzl is correct. If the "Rule Details > Scope" is set to a single project, then a branch operation like "Branch > Linked issues" will only find issues in that one project. The "Branch" component configuration actually provides a reminder about this. So you will have to use a "Rule Details > Scope" of either…

The documentation for using issueLinks in Smart Values is severely lacking right now -- please provide feedback to Atlassian at the bottom of those documentation pages! Server/DC page here, Cloud page here. Perhaps issue.issuelinks.outwardIssue might be a list? So perhaps Smart Value list traversal is needed? Server/DC…

OK, let's take it step by step. First, let's confirm that this rule is triggering properly as you expect. Add a Log Action step in your rule, where shown below by the arrow: Configure that new Log Action component to look like this: When you run your rule (by transitioning an Epic), you should see a message in the Audit…

...and Done!

This thread explores how you might go about that. (Tip: using the community search, in this case for "automation remaining", can help uncover answers more quickly.) But I really suggest you consider this question first: Do you really want to automate that? I see the biggest value of the Remaining Estimate field to be…

The rule configuration for "Projects" (which you highlighted) determines the general context for the rule, not an absolute scope for all issues processed. I see that you're branching on "Linked Issues", and I could imagine that issues in the configured project might link to issues outside that project. The trigger for this…

Well, that wasn't as trivial as it looked to solve. :-| I'll start with the solution: Priority: {{#if(equals(issue.priority.name,"1-Urgent"))}}:exclamation: {{/}}{{issue.priority.name}} which produces in Slack, in our environment: HOWEVER, we have renamed our Status names to use a numeric prefix (so they will sort…

@Bill Sheboy I did not try to actually send emails. @Tim Foster wasn't even able to get results from the dead-simple Log Action, and I saw no need to go further until he was able to get that to work. There may be issues with the separator character (semicolon, comma, etc), which I mentioned previously. Again, seemed…

@Tim Perrault The rule I shared above works fine with multiple issues/emails. I just tested it. It is unfortunate that the same email may be repeated multiple times. But the effort in Automation to de-duplicate a list would be best handled in a separate post.

Hmm, actual screenshots of your rule and the components of interest might help. At this point, all I can say is "works on my box" (works in my cloud?). See below.

One of my teams used to use a coffee can to collect pieces of paper for the retro -- old school. @Rina Nir - I just LOVE these ideas to gather data at time-of-impact, right in the Jira issues, and flow them into the Retro! A few thoughts of mine: * Configuring the two new fields to be in the "Hide when empty" section…

To help troubleshoot rules, I always like to use the "Audit log" action - in this case to see what your lookupissues smart value expression evaluates to. In my test, it looks like this: I'm guessing that's not quite what you expected (it's not an email address). It's actually the user ID, which is what Atlassian uses to…

I find that doing a Proof Of Concept (POC) can be vital to selecting Apps which meet your needs. A POC is usually focused on showing basic functionality and confirming requirements and assumptions. A POC should be very limited in time (as brief as possible), and focused on the bare minimum effort to gain confidence that…

We use Confluence pages to cover the basics at a high-level, and provide links for further reading / viewing. Our next stage is to use checklists in a templated set of Jira stories (one epic per new hire in a separate Onboarding project). Just a few stories (week 1, week 2, etc) containing several steps for them to…

If you're not convinced that Time Tracking is important, here are two articles explaining the various values that it can bring to your organization (or to you as an individual): * Why is time tracking important? (for an organization) * Why is time management important at work? (for individuals) Note: I am not affiliated…

Please note that this relates only to Company-Managed Projects. Team-Managed Projects do not use Schemes.

I'm not aware of any option to sort Epics in the panel of the Backlog view (regardless of Automation). Automation might help you set a field that you could sort by, but Automation is unrelated to any view of issues (Epic panel, Backlog view, Sprint view, Issue search results, etc). Some other options for sorting your…

First, confirm that the type of this custom value is indeed numeric. If so, I suspect the value (to the right of the colon) should not be quoted. See: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Using-smart-values Consider testing this by hardcoding the JSON with a simple number,…

Hi @Naiara Sieben, welcome to the Atlassian Community! I suspect you are looking for this ticket under the "Releases" area. As you've likely figured out, the issues there focus on the "Fix versions" field, not the "Affects versions" field. These are two independent fields. They both happen to rely on defined Versions for…