Ste Wright Community Champion

Hi @Margarita You should be able to use a Scheduled trigger to achieve backfilling. For example... * Trigger: Scheduled* Run a JQL Query... = TRUE (checkbox)* JQL - "Team (New Field)" is EMPTY * Only include issues that have changed... = FALSE (checkbox) * ...rest of rule as above here This should find all previous issues…

Hi @Zaldy Parian You'll need to... * Create a custom select list field to house the coloured dot values * Set the option values to be emojis - eg. a green dot can be found here: https://emojipedia.org/large-green-circle Notably, you cannot set the emojis as options when creating the field, you need to modify the context…

Hi @Eric Jahn You can extend your rule to copy the Status from the issue being cloned (assuming it's the trigger issue). You will need to ensure however it's possible to transition from the creation status (eg. To Do) to the target status (eg. In Progress) directly. The relevant rule details would look like this... *…

Hi @Eric Jahn You don't need to transition the issue if it remains in the first status post-creation. These additional details/rules are only needed if you're transitioning the issues straight away. Edit: Answered on your new question. Ste

Hi @Vassia Bravou Beyond emoji's in page titles, not that I know of. What were you looking to do specifically? Ste

Hi @Andrew That's fair. Did you work this out in your instance? Or still need help on how to clone the specific key? --- Edit: I did try to create an Info Panel using the "default" option I mentioned above and was able to; it uses markup rather than markdown. For example... {panel:bgColor=#ffebe6} Error Panel {panel}…

Hi @Patrick FG Are you on Cloud or Server/DC? Ste

Hi @Margarita Turina Are you using the Custom Field's ID? Usually that's a more static option than the field name (just in case there's another Team field). Otherwise, could you provide a screenshot of your Action? Ste

Hi @Mario Esposito This is possible now - check out this help page for more information: https://support.atlassian.com/jira-software-cloud/docs/change-financial-year-dates-in-your-plans/ Ste

Posting an update (as someone else posted). It is now possible to set the Quarters of your Financial Year in Plans - check out this help page: https://support.atlassian.com/jira-software-cloud/docs/change-financial-year-dates-in-your-plans/ Ste

Thanks for the review @Monique vdB - congrats everyone, especially @Trudy P Claspill for taking out the triple!! Ste

Hi @Jack Richens You might be able to do this using some further automation - eg. * Recalculate the numeric values into time, and then... * Publish it to a text field (as that format isn't possible in a numeric field) That might take some testing - I'd consider re-asking this question as a new question on the Community -…

Hi @Vjera Turk It doesn't appear it's possible to get to this screen from the new UI - but I did find a workaround: * Go to Filters (top navigation bar) > View All Filters * Ensure you're in the list view for search results * Search for the issue you want to link multiple issues to * Scroll to the furthest right-hand…

Hi @Daniel Blomqvist This worked for me: {{#lookupIssues}} * <a href="{{url}}">{{key}} - {{Summary}}</a> {{/}} ^ Only difference I can see is a space in your smart value between * and <a href... Ste

Hi @Ste404 Not natively - you could possibly do this using a script or similar through an app, but it's not a field option otherwise. Ste

Hi @Bhushan Kshirsagar Try this: comment ~ currentuser() Ste

Hi @Marvin You're looking for an Atlassian product that does that? If yes, I'd check out Confluence Whiteboards which covers some of those needs. Alternatively, I'd check out products like Miro, Mural, Spark, etc? Ste

Hi @Charles R_ DeVane That's a JQL query, when using issue search. What's the problem you're finding with it? Ste

Hi @Patrick Tryon It's not possible natively at present - but there are feature requests you can vote for, check out: * https://jira.atlassian.com/browse/JRACLOUD-82542 * https://jira.atlassian.com/browse/JSWCLOUD-23151 Ste

Hi @NAYANA In terms of Cloud migration from Server? If so - sure, installing prior to migration is the normal approach. See more information on this help page: https://support.atlassian.com/migration/docs/assess-and-migrate-apps-with-the-cloud-migration-assistant/ Ste

Hi @Michelle Monastersky You want a cloned card to automatically transition? Is there something which clarifies it was cloned from the template? EG. a link back to the clone? If yes, you could do this using Automation - eg. * If an issue is created * And, it was created from the Template (i.e it's linked to it) * Then,…

Hi @Heather Blue What does the audit log say for this rule when it tries to run? Is it possibly hitting a service limit? Do you still have enough executions? Check service/execution limits here... * https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/ *…

Hi @david jay mcgee Like a dependency map? If so, Advanced Roadmaps allows for this natively - check out dependency help pages here, and details on the dependency view on this page Ste

Hi @Jeremy Tatro Not natively; you might be able to get Automation to do this with an App which allows for these kinds of notifications (although I've not tried this). I'd check out Apps like Enterprise Mail Handler for Jira, or another App from the Marketplace Ste

Let us know if you need help to implement :) Ste

Hi @Robbie Lee (US - ADVS) I'll follow-up :) Ste

Hi @Riki YAMASHITA There's two options here (and you could do both): * Security Levels can be set as a "default" - so you could set the default to be a level L2 cannot see. You can do this using the relevant hyperlink in the "Security Level" screen, under the Actions column * If escalations are tracked elsewhere (eg. based…

Hi @Andrew Do you need to clone from another Issue though? Couldn't you just build the information to populate into each field into the Automation Rule? Ste

Hi @Caleb Park Not natively, as far as I know. This is in Advanced Roadmaps I assume? Ste

Hi @Greg Cook I'd move the Statuses to the top of the list (as newly added Statuses go on the bottom), and the Workflows should be in the "Inactive" tab. Then write it up in your documentation that related configuration is deprecated and not to be used. Not ideal in your situation potentially, but I think the most optimum…