Hey community! Sorry - long-ish post incoming I'm currently attempting what should be an easy automation but is really stumping me. I have set up a rule that when bugs in a particular space are resolved, that a slack notification occurs to let out stakeholders know that a bug has been resolved. Where I'm struggling is, that we want to "@" tag them in slack which should be easy right? GPT mentions that I could use a lookup table (I've got over 60 slack IDs to add) but our Jira (premium cloud upgraded version) doesn't offer Lookup tables as an option ?! 🥲. So instead, it recommends we use a create variable option "Reported by: <@{{var.slackMap.[issue.reporter.displayName]}}>" I've done that in the following format: Trigger: Issue transitioned → Done ↓ Condition: Issue type = Bug ↓ Condition: Project = [space] ↓ Action: Create variable (slackMap) ↓ Action: Send Slack message I tested this with just one user/slack ID and it worked perfectly! However, when I added the full list of team members, it populated with this notification in slack: "DO-1234 has been resolved in the Customer Support project. Reported by: <@> View issue" so it's removed the "@" tag that was there when I tried with one example. GPT then said that Jira doesn't support <@{{var.slackMap.[issue.reporter.displayName]}}> (Sigh) My last option is the If/Else path, but not doing that for over 70 team members and it will be impossible to maintain! Any sanity checks/advice would be very much appreciated

This is the question especially to those, who are running big enterprise instances. With migration to cloud I was happy, thinking "Cool, now Atlassian will roll out all new features for me, so I don't need to perform upgrades". I remember @Josh Golosinskiy already complained on this topic in several posts here and on LinkedIn, still I didn't figure out the good approach for myself. What’s recommended strategy to follow on new features launched by Atlassian without our control ? One thing is when new Jira space report or new Confluence macro is being rolled out, of course, I want to know when it appears in my instance, but I can live with it. But when BIG feature like Rovo is enabled in my instance of 6K+ users I definitely want to know about it in advance :D

I have an automation for JSM that needs to add internal request participants to a ticket once it's created (based on other logic we have setup), but retain the original request participants (often our client users). When I use "Edit request participants --> Copy from Work Item", the automation replaces the existing request participants instead of appending them. Thoughts on how I can achieve this?

Hi, everyone! Excited to be here! :) I’m currently working with a small nonprofit and have set up Confluence to: - Be a knowledge base - Document meeting notes - Capture project overviews & requirements As a wolf pack of one 🙃, I want to eventually add more of their users — they’d like to also have SOPs in this new space! — and I need to set up the home page to be a welcoming first stop for them. Any tips on structuring it for folks who are not familiar with Confluence, such as recommended sections? (I don’t have any apps installed yet.) Thank you in advance for any & all help! :)

What’s your advice on the best regular housekeeping tasks I should try to implement to tidy up Jira and Confluence on Atlassian Cloud to keep them running efficiently and avoid performance issues over time? Has anyone used the new Site Optimizer tools available in Jira? Personally I have found some of its recommendations a little unreliable and have been cautious about running them on our production site.