Hey everyone! As I was brushing my teeth this morning (which is usually the time I'm most reflective), I wondered how other orgs that you guys work in or have consulted with like to manage your workflows and schemes? I've worked in both a very disciplined and totally chaotic environments, and really see how essential it is to have consistency across teams. In the past, we have leveraged that by having a single scheme and workflow across multiple spaces (and with some minor exceptions for non tech teams kept a like for like mirror image of those items with some minor adjustments based on their individual team needs) But on the flip-side, if you need to put mandatory fields or validations on workflows to improve the discipline of some teams but not others, would you feel that having several duplicate schemes works best in these regards? Or do you just apply a one size fits all approach and stick with one single instance?

We are looking to keep optimizing our service project early this year and have a few add-ons in mind (which will some of our own support gaps, but also a few things JSM doesn't do out of the box). What are your top 3 must-have Jira add-ons and why?

Happy New Year everyone! Just wanted to post an interesting use case that I've discovered. I've been asked to create a Gantt view in Jira and have directed my teams to the Timeline view in Plans - works quite well and does everything that I need. However, the sad news is that it looks quite dull, very bland overall. As this was my first time looking at a plan view from a timeline perspective, I've found out that the colour of Parent Work Items and their Child initiatives (we have a hierarchy that goes one up over initiatives), will only reflect the hard coded colours based on the status category! Example: If the status of the parent or child work item is New, it's a flat grey colour. If it's Done/Released, then it's showing as green. However (and agree with my execs), they've seen lovely colourful gantt charts (obviously through 3rd party apps) that look really neat, and lots of fruit salad combinations! Sadly, with this limitation in Jira, it disappoints with its limitations....

Join our live session today at 10am CST - well be covering if story points are a good idea! https://www.skool.com/live/dS2VZJCVjfZ

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