Curt Holley Community Champion

Custom field of Theme is a great suggestion IMO @Dave 

Or....you could consider putting the "Themes" below Initiatives in the hierarchy. Not ideal, but possibly workable?

Totally agree @Brant Schroeder 

Are your Epics, Initiatives, Programs and Objectives in the sprints, or just the stories? As I believe the "roll-up" of dates comes from the Sprint dates, not the children. Thus, to inherit the dates (where blank) they would have to be in the sprint.

Agreed @Dominic Price though your 4L's was one of my fav takeaways 👍

Hi @Deon Singh Can't say I've ever experienced this....and if it is just a one-off I wouldn't worry too much about it. Could be network and/or caching oddity. Could be the browser. Mystery of Cloud.... But!!! If you notice this happening regularly, raise it with Atlassian support. Fingers crossed though, that you never…

HI @Mike Lemmon What are you using as the Issue sources? A Board, Project or filter? or a combo of/multiple sources?? Then for the board where the 2 sprints involve reside, what is the Filter Query of that board? Are there multiple active sprints, or multiple projects in scope of the filter query?

I loved the Fireside chat between @Dominic Price and Dan Pink. ❤ Highly Recommended ✅

@David Wuth we currently have the new Header and it takes a moment or 2 to get used to where everything is hiding. but once you get used to the new layout, I doubt you will want to go back. @Dave loving how the header can be Collapsed for maximum Roadmap screen space 👍

I think automation rules pertaining to sprints are better being set as Single project rules anyway. Keeps it all local, so to speak. If the sprints/boards filter multi-project info, then the automation would need to be multi-project as well. but that ups the complexity factor, for sure.

I don't have a link @anjul.khera but as @Dave has alluded to, this can be solved via Automation For Jira (assuming you are on Jira Cloud?). At a basic level the automation would go something like the below. You may need/want to get more complicated or use story points, but from what you have said, this should get you…

Thanks @Mary Raleigh We are on Premium Cloud. Will take it for a spin and provide feedback

Firstly, brilliant talk. Love the idea/ideals behind The Loop ❤ Question: Team Central, when and how can we get it? (I also wonder about cost) Perhaps other "Point A" sessions will help me answer these 🤔 #1 takeaway For me (as a Jira admin and Automation for Jira ninja) "Curate, don't automate" and the why behind that…

Aha!! that makes sense @Esther Strom and by the comments below appears to be right. I love it!!! But also love how I fooled myself into thinking Atlassian and I were so aligned. Told you it was my 1st time 🤣

Beat me to it @Dave But this would be an awesome feature

Hi folks I’m loving this group and have used it to cut my community leader teeth by posting a discussion and article here, which has been great to read about how other Cloud admins approach….things. So, I’m all the way down under in Wellington, New Zealand and am originally from Australia. Working as the Atlassian Coach…

10 albums!!! Impressive. Welcome abroad @Michael Glenn Williams 

I agree with @Bill Sheboy and if you go with option 2, If in the second (part 2) automation rule (that would do the linking) you check the 👇 in the Rule details section the timing will be fine.

You could run it on a schedule trigger...not real time, but contains the frequency

Interested @Dave and feedback submitted as suggested

FYI I've just created an article about something this discussion reminded me of Bridging the gap between Team managed and Company managed projects (atlassian.com)

Agreed 👍

Love it 👍

Thanks @Taranjeet Singh It is certainly providing me with some interesting insights.

Oh yes!!! some great tips there. Good point around Kanban boards and the "backlog' options. Presumably in each workflow you have mentioned above @Mykenna Cepek the first status is the default at Creation? Do you find people get confused about that? As in, in this project "to do" is the beginning, but in that project…

Words of wisdom ☝

Nice. Yes, that is certainly as complicated as I would ever want to go. Your workflow reminds me of another question. How conditional do you make the workflow? We have made all our main workflows "All". As in, any status, to any other status.

Totally agree. And this is precisely how our current workflows were put together, with Software and non software teams in mind, based on SAFe version 5 and with the ability for all to have a common language/understanding....continuity across all projects.

Nice. Totally agree, there are more ways to visualise work than simply adding another column/status.

Yes, part of my "Why" for this discuss was due to contemplating allowing Team Managed projects. As we have a growing band of Kanban evangelists who seem to want a new status/column for every breath they take. 🙄