Curt Holley Community Champion

Getting to know Jira Software - YouTube and the Atlassian youtube channel in general is a great resource to get you started.

It would be good to know what trigger and conditions you are using, as that could influence the solution. But at a high level, I agree with @Pramodh M use JQL to restrict or check to see if such sub-tasks already exist. 

Hi @Stacy Gardner Welcome to the community! So when you look at the filter results in Jira (via Advanced issue search) do you get 9 or 10? Am I right in thinking they are all Epics, that are Unresolved? Have you analysed what if different about the 3 that do show to the 6 (or 7) that do not? As there must be a difference…

Further to @Pramodh M advice. If the screens that you want the custom field on are shared across many projects and you only want one or some of them to have the field, then edit the "Context" and change from Global to "Apply to issues under selected projects" and select the relevant project/s.

Hi @VINCENT DUPONT That would be a nice feature to have, but alas, currently this is not doable. Why? from a pure Jira prospective, the new issue type/s you create (like Initiative) are at the story level....the only level native Jira will let you create new issue types at (unless specified as sub-tasks). Then via Advanced…

 "nobody ever died from a lack of marketing." could be argued... by many a failed artist/product. 😂

Brilliant. I must confess, I've never used that action. But now I know..... 😊👍

Interesting...I hadn't heard about Apple's desire to get back into the offices. So much for "Think differently"

Hi Ken Do you have Advanced Roadmaps currently? As you can create the higher 'Initiative' level from the Delivery screen if you do. See below example. Note: we call them SAFe Epics, not Initiatives

Do the "customers" have a Jira license? If so, you could make use of a User Picker field. If not, I would recommend grouping them and adding those groups to a picklist. Same for the skills, as you definitely do not want a picklist with over 1000 entries. As @Dave Bosman _Inetum_ has suggested, these two fields could be…

Great advice @Jimmy Seddon ❤

One of the blessings of Covid (strange opening line, I admit) is how it has force the hand of many organisations to embrace things like: * Truly flexible working arrangements...company wide! * Virtual means of collaboration (Zoom/Teams/Slack, Jira/Confluence/Miro etc.) As well as having to support their people in…

Hi @Bernd Kübrich Welcome to the community. There is no inbuilt automation that can do this, but something like Jira Command Line Interface (CLI) | Atlassian Marketplace would more than likely be able to achieve what you've asked.

Have I got this right.. you want a list of over 500 options placed into a single choice select list, that is based on (over 500) options for the "next course of action" of something. How many of these options would ever be selected? How many stories/issues will ever have any selected? A list of over 500 anything should not…

Great question! and some great answers as well. Here are the Do's and Don't I've put together as part of a Confluence based Admin Hub I'm building as part of training up new admins.

Hi @Hugo Winder What we do/have done is: * Created a Milestone issue type * Add the relevant milestones to the Epic as part of Planning * Create a view in Advanced roadmaps that only shows the Epics and their milestones. This creates an easy to view Timeline (including which sprint the milestone is expected to occur…

All you need do to get sub-tasks original estimate and time tracking to sum-up into their parent story is....use the original estimate (and time tracking) of the sub-tasks. The story will show the progress in the time tracking section. Note: it doesn't ever populate the original estimate field (though automation inspired…

No. currentUser() is just a way of creating JQL that will show what is relevant to the person that evokes it. Be it assigned to, or reported by, or any other "User Picker" field you may have. Any extra tricks are performed by expanding the JQL. i.e. project = ABC and assignee = currentUser() and statusCategory = "In…

OK, cool. But how is a Portfolio currently defined in Jira? As that is key to how to approach this. If (for instance) you used Project categories, then the JQL is something like: category = "Portfolio 1" plus any other conditions you may want to apply, like "Status != Done" or whatever. If a portfolio is defined by a…

Are the Departments groups in Jira? if so, something like this: assignee in membersOf("Marketing", "Finance") and assignee = currentUser() By the sound of it, the Portfolio isn't defined in Jira directly anywhere, is that right? Also, what do you use Project category for, as defining each project to its portfolio would…

The "For stories (or other issues in Epic)" branch only works if the trigger issue is an Epic. Try a linked issues branch

For Case#2. Can you show us the rule and any info in the audit logs?

In this case, your definition of "Portfolio" is the contents of a Jira Plan, is that right? or am I missing something??

Good point @Bill Sheboy My example is all about linked issues @Rich Evers but either/both can be done. Other complexities may arise from different workflows and or different "Done" status categories within...resolution codes (if required) etc. But all very doable. let us know ow you get on.

Hi @Rich Evers Welcome to the community. You might wanna get more conditional (I know I would), but the basic version of the automation would be something like:

Hi @Mats Rahm What you will need to do is use the "Parent link" field. It along with the "Team" field are introduced as part of Jira premium and the Parent link field is key to having a Hierarchy above Jira epics. You will need to set these up (see Enable custom fields used in Advanced Roadmaps in Jira | Jira Software…

Just to clarify, you are using Jira cloud premium and want to have an Advanced roadmaps (Plan) that shows everything assigned to whoever looks at that plan based on a filter using the current user functionality? If so, I have just done an experiment. I used the following JQL: assignee = currentUser() AND statusCategory !=…

When you have a tool like Jira, you should really look to define your format in Jira so it can be the master for all your issues, otherwise what is the point of having Jira?

Nice...looking forward to Automation for Confluence and would love to see automation expanded into the Admin realm as well.

Hi @ju Welcome to the community! Would this be for every status change? if so, how many are we talking about? What kind of estimation is done by the teams currently (time/story points)? Are they working in Sprints or doing Kanban? I'm only asking all these questions as it is a curious notion (Status change estimation date)…