Ste Wright Community Champion

Hi @Pasam Venkateshwarrao I don't know of a specific App for this - but you can search in the Marketplace for Free Apps - the option is in the Filter By options on the right-hand side in search. For example, see here: https://marketplace.atlassian.com/search?hosting=cloud&moreFilters=free&product=jira&query=capacity Ste

Hi @Povilas Urbonas What is the Rule meant to do? Is there something we can help you fix within the Rule? Alternatively, you can just disable the Rule. * Go to your Project Settings * Select Automation from the left-hand menu * Locate your Rule, and toggle it to OFF (using the slider which will be green at present)…

Hi @Gareth Jones It sounds like this feature request covers what you need - JSDCLOUD-3432 - is that correct? If yes, it might not be possible at this point - quite a specific issue though! If not, could you provide some more information - a screenshot of... * Your Portal with the logo * What the email looks like ...would…

Hi @Blerim Just to confirm... * Rule is Triggered against an Issue (somehow) * There's JQL which then runs * If the JQL finds Issues, delete the Trigger Issue * If the JQL find no Issues, don't do that ...is this correct? If yes, see below. --- You should be able to do this with Lookup Issues - for example... *…

Hi @Lara Brown So normal users can see all Issues, but Site Admins can only see their own? Could you provide details of how you set up the Issue Security Scheme? A screenshot would be beneficial here :) Ste

Hi @Wim Muyllaert Can I clarify the logic here? * You are creating Issues using Automation * Each time, it should link to all other Issues previously created by the same Automation Rule Is this correct? If yes, a few questions... * What link type should this be using? * Does the Project have just Issues created using this…

Hi @Charles Cochener View (1) is an Advanced Roadmaps plan - where this isn't possible at this point. There is a suggestion for it though, which you can vote for/watch - see: JSWCLOUD-20940 There would be some challenges to implement this though - see a good explanation of these in this previous answer, from an Atlassian…

Hi @Daniel Beckett I don't believe you can do this at present on the Change Calendar - what it can do is listed on the help page - https://support.atlassian.com/jira-service-management-cloud/docs/show-change-requests-on-the-change-calendar/ A few alternatives include: * Consider using Advanced Roadmaps, which might be able…

Hi @Danilo Simic Not that I know of using native functionality. I'd recommend either... * Create an initial Status Issues go into, which can then have a Condition to get out of, requiring a P1-P3 Priority * Remove the No Priority Set Priority - and set the default Priority to P3, so it's detrimental to not change it to the…

Hi @Onur Cevik I'm going to assume you're trying to create a Project using the configuration from another Project - and that Project is Team-managed? If yes - Team-managed Projects can't be used in this manner because as the error says, their configuration cannot be shared. It is unique to each Project in isolation.…

Hi @Greeshma Suresh Shouldn't do - but ideally Board Owners/Admins are an active account. Ste

No worries! If this answer helped resolve your question - could you accept it? That means others who find this question in future know this answer can help them too :) Ste

Hi @Jill Vieregge I think you can manage product access separate to Group membership - but it's likely not efficient to do so, especially if you have SSO/SAML or intend to use it in future. I'd either... * Separate the Product Access Groups from Groups used for other access/permissions, or... * Add Group Product Access to…

Hi @Christopher Barron Not natively - releases are locked to a single Project only. There is a feature request for this though - vote for/watch: JSWCLOUD-16637 You might be able to do it using Automation though? See this answer which has a good explanation of how this could be done. Ste

Hi @dan_ryan Your filter should include those Epics also, you could do it like this: project = ST AND ("Epic Link" in (ST-2458, ST-6053, ST-6332, ST-6333, ST-6988, ST-6975) OR key in (ST-2458, ST-6053, ST-6332, ST-6333, ST-6988, ST-6975)) ORDER BY created DESC Let us know if this works! Ste

Hi @Lisa Garrett Expanding on Samuel's point, you can view a list of all Atlassian Community Event (ACE) Chapters from this page - https://ace.atlassian.com/communityevents/ A list of all Chapters is down the bottom of the page, under the title "Find events near you". Here you'll be able to find Community Leaders in your…

Hi @Kathy Barton Not that I know of - you do need to exclude the Epic (eg. using AND issuetype != Epic) This function has included the Epic for some time I believe - but it could be a Bug?. You can create Bugs for Atlassian to review here - https://jira.atlassian.com/secure/Dashboard.jspa Ste

Hi @Dietrich Lehr {{page.title}} should work - this is the smart value for page title. I tested it also, and it works fine for me. What's the rest of your rule look like? A screenshot of it might be beneficial :) --- Edit: I tried this using your Branch - Related Entities - and had the same experience. So I tried using…

Hi @Piotr Ptak As far as I know, this isn't possible at the moment. You could create a suggestion for it though? You can do this from here: https://jira.atlassian.com/secure/Dashboard.jspa Ste

Hi @dan_ryan First thing I'd check is the Board Filter - to do this: * Go to Options (3-dots icon in top-right) > Board Settings * Select General from the left-hand menu * Ensure the Filter Query includes the Epics - eg. it's not limited to just Stories or Tasks, or the parameters don't exclude Epics, etc * If they are…

Hi @Hussein Dbouk Sure, this is possible. Just remember though that with created date, it orders by both date AND time - because that is its field type. If you want to order by only date, then you'd need to... * Create a Date Picker custom field - eg. Created - Date Only * Automate the population of this field at creation…

Hi @Aykan Inal Possibly the rule explained in this help page? If yes, it still used Automation, just the Legacy version of it. The version recommended above is the newer, more future-proofed version of Automation :) Ste

Let us know how it goes! Ste

Awesome, glad it works! If this answer helped resolve your question, could you accept it? This helps others who find the question in future know this answer can help them too :) Ste

Hi @Harry Bos Move should be fine. Move effectively is changing the Project and the Key - the rest of the data should remain as-is if the configuration is the same :) If not there might be some other changes - eg. different Statuses (which you'd map to), etc. Ste

Hi @홍종표 Just confirming from the above - is this rule working for you? Or do you have questions? :) Ste

Hi @Edward Dighe You don't need Sprints to have the Backlog turned on. I'd probably recommend one of three things (simplest > complex). * Turn off the Backlog * Move to a Company-managed Project * Try to utilise Automation --- (1) Turn off the Backlog This is a straight-forward solution. If you're looking for a method to…

Hi @[deleted] I'd recommend prioritising implementing the Form into Jira. It will be significantly easier than trying to make this work in Automation (which I don't think is necessarily possible for the user, as this works off Account ID, not name/email). Ste

Hi @Trevor Overstreet This shouldn't be the case - I tested this prior to recommending it. Could you clarify... * Epic Name is still on the Screen (doesn't need to be on the Request Type Form) * The Request Types are still setup as before * This Epic is being edited, not cloned/moved to another Project ...? --- It might…

No worries @Susheela_Kushwaha - let us know how it goes! --- @angelicagavino - I think there's limits in Expressions like in JQL. Because "is not EMPTY" or "Null" is not an available option for Parent Link in JQL, so might be similarly unavailable in your use case. Ste