Curt Holley Community Champion

Unless they are particularly complex rules, then exporting to Git seems a little extreme for a rule not even currently in use. And yes! definitely rules get modified all the time "in the wild" and I don't see that as an issue. That said, I find it easier to train newbie's up in writing and testing automation in a "lab", as…

Similar to all of the above....I have a test project which is where all rules are built. They are tested and when ready copied or simply moved and configured for their "in the wild" usage. Notes of constraints or side'effects noted in the description. Pending on the complexity, changes to rules are either done on the fly…

Do you have scriptrunner or some automation tool? As you could get the automation to add the dates for you

Hi @Aaron Gage I'm only familiar with Cloud, but it is the same as you describe. Question: you are rolling up dates from stories to Epics (that don't have dates set) is that right? I would have thought, if the same stories are in multiple plans....they are still linked to the same epic's, which would be linked to the same…

Most people that know me through Atlassian (or work) don't know that I'm addicted to funky (and or electronic) music and that my "in" to technology was via music software and before that hardware (that could be programmed) That I was a drummer in a pop group in the 80s (see photo below) Became a Club DJ in the 90s and…

Love it! Rock on

Definitely doable. This should help: Teams | Advanced Roadmaps for Jira Cloud | Atlassian Documentation

Hi @Gonchik Tsymzhitov No, but I'mtalking with our account manager today about it and she is going to find someone for me to show it to. Thanks for the interest/advise.

Footnote: You may wanna add in conditions around not updating the dates if already populated? Up to you, Just thought I'd add this, as the above will overwrite any existing dates, which might be what you want, or not. ☮

Good questions! and TBH I'm not sure of the answers as I/we have never run into any issues. Here are my observations from PI planning (remotely) using a single plan, but with multiple views. We had, a plan with a "Master view" (issue source = entire (newish) project). We have "team" filtered views for 5 different teams.…

Hi @Artur Franczuk Not sure if you are using Jira Cloud or not, but assuming you are, then using Automation would be the way to do this. Setup a rule along the lines of: Trigger = Field value changed (field being fix version), on edit and create. Condition = When Fix version is not empty Action = Edit issue (and set up the…

Yes, that can be done. It just pays to have a plan (no pun intended) about who and when people update the changes back to Jira.

Hi @Alden Sova Welcome to the Atlassian community. What I would do is: * create two "landing" pages (A tool and B tool). * create 2 versions of the template (even if the only difference between them is the different label) * On each landing page add the "Create from template" macro and configure them to use the relevant…

Yeah, I agree with @[deleted] and co. Votes for all. Option B

Yes @Jay Egan I imagine so. The exclusion rules are in the Plans configuration. You should be able to access and set per plan. A word with the Admins is a good idea though. Good luck!!

OK, cool. Now all you need to do is configure "Exclude any completed issues after" section so that they are back in the plan.

Right. Perhaps doing via a scheduled rule using JQL is the best bet. Not real-time/ideal, but a means to an end??

Hi @Kaj Sennelöv one great feature of Advanced Roadmaps is the ability for it to "roll-up' info (like story points) to the higher level Epics/Initiatives etc. Likewise, the ability to choose to still see the full hierarchy when filtering could mean that you don't need to automate the code and labels from top to bottom. as…

Hi @Jay Egan Welcome to the community. I can only imagine that no Epics meet the criteria of "Complete" within the bounds of the Board's filter query. If you take the boards filter query and adjust it to incorporate: type = Epic and statusCategory = Done So that you are filtering under the boards usual conditions but…

Hi @Madhu Reddy Automation for Jira certainly is part of cloud. If you can get to the "project settings" of a project, you can access the "Automation" section for that project. It's worth noting, if you are on Jira standard, multi -project and global automation rules have monthly execution limits. See @Linda Milne_Togetha…

Hi @Olga Kolov Go to the more options section of the Edit issue action. Then set it up as per the screenshot below. In this example I use Team 6. You just need to know the ID of your team. Procurable via JQL using "Team[Team]" = not just Team = that way, you can type your teams name and JQL will change it to the ID for you.

If you are talking about sub-tasks of Stories, then it is the Parent, not the parent link field (which is used for the hierarchy above a Jira Epic). You can have labels from a parent copied into its children (sub-tasks) via a post function in the workflow itself.

Totally agree with @Kathi Paquet If management can't come to the work or even bother to find the data in Jira (not hard), then DO NOT give it to them the sprint report on a platter. Especially if the team do not look at it (at their retros etc..)

@Linette George If you are on Jira Cloud using the built in Automation for Jira (which I'm guessing you are?) then this might be helpful. Use smart values to access listed values | Jira Software Cloud | Atlassian Support

Hi RSavage@stellarindustrial.com Welcome to the community! If a project says it is a "Business project", then it is a Jira Work Management style project, which don't have the ability to have sprints. You need to create a Jira software project and use the Scrum template to have the ability to create and work within Sprints.

These are all great new features....particularly the CRONless schedule for someone in the southern hemisphere/NZ time zone.

HI @Chase Wilson All great news. Regarding Calendar colour options....custom field springs to mind as well as Labels and maybe even issue type. Whilst on issue type on the calendar view....what would really help me today would be the ability to filter on the Calendar by issue type. I'd give that a 3.5 Regarding nesting,…

That is how it works for me/us @Marie Peters What is the issue source for the plan? For the above I simply used the whole Project. Although the hierarchy is not all that evident in the JWM project itself, it falls right into place in AR. Note: I did have to add Epics and the Release custom (story level) issue type into the…

Hey @Marie Peters Because JWM project are Company managed projects, you can visualize their content in Advanced Roadmaps. This is a way to get the hierarchical structure visible from your JWM projects. Here is a real life example of Epic, to (in this case custom issue type of Release) Story level with sub-tasks

* What @Dave LIAO said ☝ and the ability to designate issue type for a form. 2.5 * Ability to nest across Jira hierarchy (from Epic to sub-task would do) in Timeline and Board view. 3.5 * Ability colour code by various options (not just status) on the calendar view particularly, but could be cool on other views as well. 3…