Figured I’d introduce myself. I’m Arslan, a Solutions Engineer, Atlassian Certified Expert, avid runner, husband, and nerdy uncle seeking to continually learn, grow, and share with awesome individuals. Why’d I join this community? I discovered and began engaging with @Alex Ortiz’s and @Josh Golosinskiy’s excellent webinars and content since earlier this year (renewed my certs). They’ve been very helpful in addressing my Atlassian platform knowledge gaps and more while making it fun, to say the least! So joining this community was a no-brainer. I’m also currently exploring the job market and reflecting on what to pursue that resonates with my values and strengths. I look forward to contributing to this community and any opportunity to engage! -Arslan linkedin.com/in/arsiqbal

Hi there! My DONE work items from last sprint are showing in this week's new sprint's DONE column. I don't have access to the Jira work item workflows yet in the account from the client, but thinking this is culprit. What's your take? Thank you!

Any recommendations on how we promote changes we made and tested in our Dev environment into Production?

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