Ste Wright Community Champion

Hi @Sreenadh Is this related to your other question? In the other question, the rule copies the Status from the Sub-tasks to the Parent - but the logic in this question appears to be the opposite... * If Parent CR transitions to "In Development" * Then copy this Status to its Sub-tasks ...is this correct? Ste

Hi @Sreenadh On the Action (on the final screenshot) - Transition Issue - try closing the "More Options" drop-down menu (so it's not visibly open). Then publish the change, and retest the rule. If this does not work - could you provide a screenshot of the audit log, with the specific error that is occurring? Ste

Hi @Ryan Hamilton The rule looks correct - but it's likely in the Branch you have this checkbox checked: * Only include issues that have changed since the last time this rule executed To ensure this rule transitions the linked Issues every time, ensure this checkbox is UNCHECKED/FALSE. Let us know if this works! Ste

Hi @Ingmar Heinrich It's a good question! There are other suggestions for this you can review - for example ID-6457 (which you've already commented on!) There used to be "nickname" field on your Atlassian Account profile also at a point, I think it's now called "Public Name" (i.e the name used on the Community forums). The…

Hi @Miia Toivanen There is a feature request for this that you can vote for / watch - see: JSWCLOUD-23267 Ste

Hi @홍종표 Because a Select List is value based, and an Epic Link is Key based, I think it'd likely be easier to set this using IF/ELSE Conditions. It shouldn't be too bad if there's only 4-10 Epics to do this. --- This would be a separate rule from the "Create Issue" rule - the rule would look something like... *…

Hi @Wanda Gomes You need to make decisions on how to setup your Project(s). For example: * Are Software and Hardware tasks done by different teams? Or are teams cross-functional? * What does a Jira Project represent - is it a team? A product? A project? * Should these tasks be different Issue Types? Or are Issue Types…

Hi @RonnyBonny Fix Versions are Project-specific - natively, they're not shared across Projects. You can either: * If you have an older version of Advanced Roadmaps, you can manage cross-Project releases within Jira from there * Use an App, such as Version & Component Sync for Jira - or another App from the Marketplace Ste

Hi @Mister Femi Yes, this query is showing Issues which are in 2+ Sprints, where one is closed, and the other is active/planned. You could customise it based on whatever other logic you need - for example if it's for Stories which are not closed/done, it might be: issuetype = Story AND resolution is EMPTY AND sprint in…

Hi @Martin Kohout There are a few options... --- Workflows You could try creating this with Conditions/Validators - for example: * Create a custom Group Picker field - Approver * Limit the transition that needs approval, using a Condition - i.e. User Is In Group Custom Field - so only specific users can transition the…

Hi @Wanda Gomes Are you looking for a template Workflow? There are lots of Project templates available across Jira Software and Jira Work Management - you could look if one would work for your team? You can also see more details about what each Project includes if you can Create Projects: * Go to Projects > Create Project…

Hi @Miia Toivanen Just to confirm, you have: * An Issue Hierarchy where Epics can have parents (via Parent Link) * The need to locate Epics with Parents, where the Parent has a specific label --- If the above is correct, this isn't possible with native JQL, because it does not support sub-queries (i.e Parents with a…

Hi @carl vincent dilig This looks like Jira Server/DC, not Cloud. If there's an option to re-open your Risk, it should be a Status button just above this information. It could be called anything, but it might be a previous Status name, or Reopen, or similar. If it's not there - you can check whether it's possible to reopen…

Hi @Nina Eickeler Not that I know of. There are some suggestions which are related - such as... * JRACLOUD-74800 * JRACLOUD-75364 ...which you could vote for and watch. Otherwise, if you don't want to see these - I'd use your email service's filtering rules, to put these into folders and/or make them unread :) Ste

Hi @carl vincent dilig "Retired" isn't a term used in Jira normally. You might have: * Deleted it - More (3-dots icon) > Delete * Transitioned it to Done (perhaps Retired is a resolution) - either by changing the Status, or moving it on a board * ...or something else The right solution for you will depend on the action you…

Hi @Barış Özer Just to clarify, Status and Resolution are two different fields. If you're looking for just Issues with a Status of Resolved, and the Resolution can be set to anything (including empty) - then the "resolution is not EMPTY" part of the query is not required. To see how Status and Resolutions differ, see this…

Hi @Mister Femi Does this work for you? sprint in closedSprints() AND (Sprint in openSprints() OR Sprint in futureSprints()) ^ This provides all Issues: * Which are in a Closed Sprint and... * Are in an Open Sprint (i.e an active Sprint) or... * A future Sprint (i.e a planned Sprint) Ste

Hi @carl vincent dilig What's the definition of "retire a Risk" in your instance? Do you mean you deleted it? If yes, deletion is permanent - you cannot recover it from within Jira. You could contact your internal Platform Admin Team and see if they have a recent backup of Jira - and if they can recover it that way? --- If…

Hi @Barış Özer Yes, yours also works the same way :) I usually avoid "Unresolved" in resolution queries, in case someone creates it as a resolution option! But your JQL should produce the same results as what I suggested. Ste

Hi @홍종표 Can I clarify the need here - is it: * An issue is created using an Automation Rule * In that rule is a custom select list with a list of Epics * Depending on which option is selected, it should select the corresponding Epic Is this correct? If yes * How many Epics options are there? * Is "Epic Link" the Select…

Hi @Barış Özer Can I confirm the logic for your rule is: * Project = SD * Status = Resolved * Resolution is not empty * Assignee = User * Date = Created - created during last year --- If this is correct, this should work: project = SD AND status = Resolved AND resolution is not EMPTY AND assignee = 62069a8aed02400069a3ad5f…

Hi @Umar testing You don't need the arrows (< >) in the actual rule - when I put "<Timezone Here>" that just shows that the location is placeholder for a timezone value. So as an example, one the Condition smart values will be: {{now.convertToTimeZone("Asia/Riyadh").dayofWeekName}} Ste

But do other users receive Notifications, based on whatever other notifications are sent? Ste

Hi @Daniel Vansnickt Do Notifications work for others users? Ste

Hi @Piyush A (STR) As far as I know, no it doesn't. Ste

Hi @darshil trivedi Just adding to this, as there's various options/answers on this question, there is a help page which details the differences between: * Share With (on request form) * Share With+ (on the customer portal post-creation) See this…

Hi @[deleted] Trello Premium is applied per Workspace - so if you have two Workspaces, you'll need to pay separate billing for them (even if the Users are the same across both). You can have unlimited Boards though within one Workspace on a Premium Plan. * To see what features each plan level has, see this page: Which plan…

No worries! I would recommend testing it in a separate Project if possible (i.e a test/dummy Project). That way you can trial different scenarios without impacting actual live data, or waiting 2 weeks each time to try different things! Ste

Hi @Saurabh Chaudhary In relation to roll-ups and seeing estimates / percentage complete, see these pages for how these work: * https://support.atlassian.com/jira-software-cloud/docs/roll-up-values-in-advanced-roadmaps/ *…

Hi @satouysq Just to confirm what is happening: * This is a chart based a Sprint * The red line is reducing pre-Sprint when changing the Remaining Estimate * The green line is staying flat when logging Time Spent until the Sprint starts ^ If yes, as far as I know, this logic is correct - this is because: * The Remaining…