Curt Holley Community Champion

Love it!!!

Make it a permanent feature where you can choose the emoji you want to "rain".

Hi @Matthew J No, not by default. but as https://support.atlassian.com/jira-software-cloud/docs/filter-changes-made-in-advanced-roadmaps/ shows, that option is only a couple of clicks away.

Go to: Plans/Settings/Advanced Roadmaps dependencies and add the desired dependency types

Hi @Tommy Bergquist Welcome to the community You will need to alter how long "done" issues show in the plan for (see below)....or create a copy plan that doesn't show them at all. As what shows on the report is what is filtered into the plan via the Issue Sources. Go to the Configuration of the plan and adjust "exclude any…

Hi @Ben Weisman It is true, when using the "Team" field, like Sprint, Sub-tasks have to have the same as their parent. The workaround is, go up a level in the hierarchy. As in, use Epic for the stories and Story (or task or whatever) for what were the sub-tasks. As "standard" level issues can be separated from the parent…

In the plan, go to: Configure/Issue sources From there you can add Projects, Boards or Filters. Add or change issue sources in a plan | Jira Software Cloud | Atlassian Support

Hi @Saikat Das If you only want that Epic and all its Story level issues and their subtasks in the plan then use this JQL: issue in portfolioChildIssuesOf(" EPIC-1") Otherwise, you could just add the whole project to the plan or a board that filters all of the relevant content, if one exists?

Really cool challenge @Christine P. Dela Rosa Remembering the importance of those "little things" in language and the impact they can have is all too easy to overlook in a corporate environment. Things like; * Remembering to ask "if now is a good time" before interrupting someone from their work (an advantage of remote…

Because Product Discovery projects are "team managed" (under the hood) and it is likely the Jira software tickets are from company managed projects, you will need to be careful. Especially as there will likely be a number of fields that are different between the two. See: Migrate between team-managed and company-managed…

You're planning a release for 2026....and it needs to be on a roadmap urgently. There is a certain irony in that statement. I mean you can create the release in the project with a date that far into the future... it will show up on the roadmap in a few years' time. Something to look forward to in early 2025. 

I'm with @Johnny FromCanada on this. Plus, any other option will be more complicated, take longer and cost more than clicking the "create Sprint" button 52 times. Which once you do the first one and set-up the weekly cadence required, is dead easy. Pro-tip: make sure the first sprint's name ends with Sprint 1, then Jira…

Hi @Ken Young What is it you are trying to achieve with this rule? Perhaps if we could see all of the workings it would make it easier for us to assist.

Card level is the best that can be done...out-of-the-box If you are on cloud, you could create an automation rule that sends a notification to * The Engineers inbox * A Slack or Teams Channel Personally, I like the card colors as it brings the issue to the whole teams attention, not just the person looking at it. Another…

Hi @Shubhangi Khandelwal Have a read of Warren's reply here. Solved: How to Use JQl to color cards (atlassian.com)

Hi @Nauman Raja It is because you are not using cloud. You will need to ensure you select the data center/server product (see below) But you will need to talk with an admin of the site to get the SEN (Support Entitlement Number)

Not really @Nauman Raja Daniel's advice is sound. If you can't work it out, talk with your Jira admins and if they can't help. someone raise it here: https://support.atlassian.com/contact 

OK @Salim Bouassida @Bill Sheboy I have it working...at least to email, but theory is the same for Slack. Schedule trigger (no JQL) Lookup issues action with sprint in openSprints() as the JQL. Send email/Slack action with: {{lookupIssues.first.sprint.distinct.goal}} 

Hi @Dyllan O'Brien For question 1: No, you need to map the form fields to Jira custom fields to be able to search via JQL or "grab" for use in automation rules. That said, I'm pretty certain that is going to change in the not too distant future. As for question 2: Have a read of this (but, not really)..... Solved: How do I…

Option one is the go for sure!!! A much better solution indeed @Bill Sheboy ⭐

Hi @Salim Bouassida It is going to be to do with the fact that you have the JQL in the Scheduled trigger. As that means the rule will action for every issue returned from that trigger. So, at a high level, you need to have a JQL that will only find one issue. Best idea I can think of (off the top of my head) is add a label…

Put simply @[deleted] until you have more than one portal you haven't really evoked "Help Centre", just a (Singular) portal page. It is somewhat misleading as the Channel is called "Help center" from within JSM. Premium is a sweet (spot) level to be at (for many reasons), but the extra $$ always needs to be factored into…

My guess, it will be to do with the number of features that are "Done" and what number of days the plan has in the "Exclude any completed issues after*" section. Are the features that you can't find in a "completed" (statuscategoory = Done) state?

At the expense of stating the obvious @Roemer Bakker You would need to create another JSM project (and thus Portal), then you could use Topics, even if the 2nd JSM project is barely used.

I'm with @Bill Sheboy on this one. You have formularized story points to = 8h You have a desire for estimate Vs actual Dev time Vs QA time All of this can be done 'out of the box' using the time tracking setup in Jira....which you are using anyway. This is a case of no point using story points.

The simplest solution here is to have your "escalated" status in Project A, set up a queue showing only the escalated tickets (in project A). Allow the already licensed agents (or a subset of) access into Project A so they can work on them there. Thus retaining all data gathered within and ability to communicate with the…

@Sushant Koshy do you need to be full blown Org Admin to create, configure and publish Topics? As I can't publish (despite being able to access, create and set it all up) in sites where I am a "site admin", but am able to in a site where I have "Org Admin". 

I'll third Darryl's advice. 👌

Which simple metrics are you talking about? (That require excel)

@Varad Pingale Is the View Projects permission actually plural, or singular? As in, if not applied in project A, but applied in project B, does that mean they can not find project A in the Project directory/JQL etc. but can find project B and any other projects they happen to have the view projects permission for? If by…