Curt Holley Community Champion

But at least we know how @Matt Goulet really feels about Confluencee.

Hey @James Webber Are you on Cloud (I can't recall)? If so, have you investigated the Data lake option? Comes with Power BI integration...out of the box! Data Lake Early Access - Atlassian Community

WFH is trending, that's for sure. I like the balance of the two and the autonomy to be flexible within them.

If you are focusing on ensuring everyone is pointed in the right direction (they know why, when and where they are going) and they get there successfully in a timely manner. Isn't that the definition of Outcome focus? I think it is important to drop the old "productivity" terminology, so as to assist reset the thinking…

Hi @Benji Purewal I can see how this could get tricky, just using JQL. especially trying to pull the whole hierarchy from a sub-task level. Question: Is this work always going to be with a single Jira project? or could X be reporting and assigned to work across lots of different Jira projects?? What I'm thinking is, it…

Hi @Priyadharshini Ammu Welcome to the Atlassian community! The first thing that comes to mind is: Is the missing Epic in a "done" state? and has it been "Done" for more than are set in the Exclusion rules??

HI @Coby Fuller I doubt it...there are so many elements that could block this even if theoretically possible. What I've seen done is create a story/task (whatever) that represents their piece of work. include the reference number of it at their end and keep as in sync as possible via stand-ups, regular catch-ups.....not…

Right, Team Managed project is a key piece of information. Off the top of my head, perhaps an Automation rule? When Epic transitioned to Done, update the Epic Status field to Done.

No, you don't have to, but that is how you ensure your epics are Done/Done/Done. This is good: Solved: How to hid completed Epics in the "EPICS" side vie... (atlassian.com)

Hi @Mark Brierley Welcome to the Atlassian community! I just do a filter like this project = XX AND (type != Epic or type = Epic AND status != Done) ORDER BY Rank ASC But....this is a way of syncing the issue status (in the workflow) with the Epic status: Linking Epic Status to the Epic Issue Status | Jira | Atlassian…

HI @Khai Bulatao Plug-ins are great and provide nice visualisation/reporting options. But you can get started by simply creating a Risk issue type and giving it some relevant custom fields (Impact, Likelihood etc). You can also give them a custom workflow based on Risk ROAMing. This is a free and easy way to get started.…

Nice one @[deleted] that makes sense. You could likely workaround this by If/else statements around each potential result from your variable and then put each corresponding Project key in place in the Create issue action. But that sounds a bit tedious :-(

Hi @Esther Strom not really. Currently you can only "Group by" Team. Which sort of does it (if everyone has shared teams set-up and in use), as it groups the items into their teams. Which gives you a cross team view, which will allude to a cross project view. What I have done is create automation to comment on External…

Excellent news @Rohan Swami !! So I take it the hierarchy stays the same, it is just the ability to (globally, in a cloud instance???) rename Epic to Feature (or whatever) and all other functionality of the current hierarchy (Initiative/Epic/Story/sub-task) would remain the same? Including the Epic and Parent link…

Hi @Deepika.Kanaparthi Welcome to the Atlassian community. It is not possible to insert a hieratically level in-between Story and Epic, only above Epic. You can have Features at the same level as Stories, but that doesn't sound like what you want. I would suggest that you use Jira epics as your Features and create a SAFe…

Hi @[deleted] if your Epics have those fields, then they can be added to the stories. Talk to an Admin and ask about having them added into the relevant schemes for use at the story level.

Hi @Andre Powers Welcome to the Atlassian Community For your first paragraph, simply configure the plan as below. i.e. have Due Date as the end date for the plan and make sure the tickbox is ticked to enable sprint dates when issues don't have dates. For the 2nd paragraph, you would need to do some form of automation to…

I/we do the same as what @Joe Lagana-Jackson has suggested. This centralised approach to the high level "Initiatives" also makes it easy for senior leaders to find them and puts them all in the same backlog/funnel. I encourage it as the best, scalable option.

So {{productSuite}} equates to a custom field with the Keys of certain other Projects as it's values, is that right? Then you want the automation to use whatever is in that field as the destination project of the Bug the automation is creating....I'm I still on the right path here?? If so, wouldn't be…

It can/done currently. Simply link them using an in scope link type for your Advanced roadmaps configuration (Talk with an Admin if you are not sure) and the dependencies will show up as badges or as lines (again, if the Plan has lines set in the Vie settings and both ends of the dependency are shown on the Plan's…

Have you considered upgrading to Jira premium? That would resolve the "limits' issue you are facing as well as add features like Advanced roadmaps. We ditched 2 apps (one automation based, the other a portfolio view of JIRA content based one) to cover the costs of premium and have never looked back! Jira Software Premium |…

Hi @DiAnna Wages So, what is the hierarchy that you have in place? Do all of these projects have Initiatives (or the like) set-up in them? or are the higher (than Epic) level/s centrally contained in another project? What are the issue sources used in this plan? Whole projects, boards or filters? are the higher level…

A simple option could be (if fit for purpose), simply export the issues from the relevant project to CSV (all fields) and import that content into a new destination location project. manually create any Components and Versions/Releases required in the destination project prior to the import. Align or enhance workflows and…

You should be able to see Original estimate and Time tracking....and they should provide all you need (without automation). Can you not see these fields in your instance?

For the record: I've done one final enhancement. Local time zoning the Last Transition occurred field/variable entries.....so the days are aligned with the users perceptions/expectations.

@Rich Wolverton I've never encountered any performance issues...not that I'm in that large a company (in the grand scheme of things). But it does have a throttle that it may deploy if you go crazy with a scheduled job. I find keeping automation real-time keeps it all under control. I have done some large bulk update type…

Love it @Darryl Lee but that is more fun than I can handle today 😂 Next phase though for sure!!!

HI @Steven Haworth I'd like to think it will be used to (if/when required) analyse where in the workflow the hold-ups are, which can lead to conversations about why. As well as how to fix moving forward. Particularly handy for Kanban teams with many workflow statuses. At the end of the day, I just build it. That said, I do…

STOP THE PRESS Thanks @Mykenna Cepek for the variable inspiration. This is why I love this Community ❤ By creating a variable {{LastTransitionTime}} out of {{now.diff(issue.customfield_10299|now).abs.businessDays}} The 1st Rule can now do it all, by using the variable as follows and finishing the rule with the update to…

HI @Mykenna Cepek you are right on all fronts. All transitions are recorded and added in sequence to the StatusChanges field. Yes, the 2nd rule is simply a timing thing. I like the sound of your variable suggestion and variables is one area of Automation for Jira that I haven't got to.....so I'm off to experiment now!!…