Ste Wright Community Champion

Hi @Bea Tea Just to confirm you are looking to create a JQL query that will show you... * All Epics in Project A... * ...that have a direct Parent which is not in Project A? ...is this correct? If yes, this isn't possible with native JQL - but there are a few options... --- Option 1 - Apps There are Apps which extend the…

Hi @Cindy Snow I think so! Apart from Option 3, which is have two Jira/Confluence instances completely separate, from one for internal teams, one for external! You'll still need to test this to ensure it works, but if in Customer Access you're going to "Allow Customers to create accounts", you probably want to go…

Awesome! Let us know how you get on :) Ste

No worries! If this answered your question, could you accept it? This helps others who find this question in future know that this answer can help them too! Ste

No worries! If you do have any further questions, please do post them on the Community - we'd all be very happy to help :) Ste

Hi @Adamscutler87 This help page details how to manually run this type of rule. Your rule is called "PO Import & Validation..." - it is possible to run from the "More" menu you have open in your last screenshot. The option to run the rule is in that list - it's the second up from the bottom, inbetween "Delete" and "Apply…

Hi @Evalaji Jones For custom Notifications, I'd recommend using Automation. This would allow you to send Notifications based on specific scenarios like a Priority of "Highest" to specific users. --- To access Automation at a Project Level, you'll need to be a Project Admin and then... * Go to Project Settings * From the…

Hi @Sharon Jacobson That doesn't show the results though, just the front page. Ste

Hi @Jorge Pérez Are you looking for the original value of the Due Date field? If yes, every Issue has an Issue History, which lists all the updates made to an Issue over time. To view this: * Open an Issue * Scroll to the bottom * Select the History tab You can then search for when the due date was changed, and what the…

I had a few wins on the Community just today! * I got my 750 accepted solutions badge! * I achieve Level 12 - Golden Seed for Kudos! Ste

Hi @MHassan Strange! As this is for Jira Service Management - and assuming the internal users might not all be Agents (i.e some could be Customers) - I would next check they are set up correctly with the right permissions: Check out these help documents: *…

Hi @Rajesh Konda Awesome! Glad you found a solution! Good luck with your migration :) Ste

Hi @Wanda Gomes Antonio I noticed this question just as I was posting on your other question! Posting my response here also! --- You'll need to consider your own internal processes, alongside each team's needs, when deciding how to structure Jira. Originally, I was going to send you a big list of things to consider - the…

Hi @Wanda Gomes You'll need to consider your own internal processes, alongside each team's needs, when deciding how to structure Jira. Originally, I was going to send you a big list of things to consider - the difficulty is though that we don't know how your company is structured, nor what reporting/visibility is important…

Hi @Meates Underwoodson Can I confirm the logic is... * If a specific set of Customers (Reporters) raises and Issue * Then add a specific Request Participant * ...and repeat, for multiple scenarios ...is this correct? --- If yes, I'd recommend using the If/Else Block condition within your rule to allow for multiple…

Hi @abhishek_gupta Is this a Company-managed or Team-managed Project? If it's Team-managed, the option to "Move child issues" will present itself. If this is Company-managed though, there isn't this option. This is because unlike Team-managed, Company-managed Projects do not require an Epic and it's children to be in the…

Thanks for confirming - and for posting the link here, which could be useful to others in future :) Ste

Hi @Rajesh Konda I know you state you have Org Admin in both the source and destination sites - but could you confirm you are an Org Admin as defined in this help page? Ste

Not a problem! If this answer resolved your query, could you accept it? That helps others who find it in future know that this answer can help them too! Ste

Hi @Sreenadh For the second set of Screenshots, this error usually happens when the Rule's Actor does not have Permission to either see the Issues, or transition them. The Actor can be found in Rule Details, is this set to a specific user? Or Automation for Jira? --- How to check the Project's Permissions will depend on…

Hi @Sreenadh This all looks correct! Have you tested it? Does it work within your instance? Ste

Hi @ISABELLE TEIXEIRA ALVES Can you confirm that you have... * Transitioned an Issue to Completed accidentally * Want to reopen it, but there's no option to ...is this correct? --- If yes, you'd need to modify the Workflow to allow for a return to the previous step if the transition does not exist now. Depending on the…

Hi @Dureid Is it a Project or a Board? These two items have names, but how to change them differs. There's also the chance if you did create the Project the Board will also need to be changed separately. --- Project Type The process differs also between the two Project Types - Company-managed and Team-managed. To tell what…

Hi @Evalaji Jones Assignee is a single user picker, so only one person can be assigned to an Issue at a time. If you're not keen to use Sub-tasks, I'd recommend considering: * Watchers: This field can include multiple users, often used to allow users to "follow" another Issue. You can see more information on Watchers on…

Hi @Sreenadh Because it's not a Sub-task, the rule won't execute the action. Your rule's logic is: * Trigger: Issue Transitioned * Condition: Issue Fields Condition* Field = Issue Type * Condition = equals * Value = Sub-task - this is what is stopping the rule for SDPD-1106 SDPD-1106 looks to be a Change Request - a…

Hi @Sreenadh Awesome! Because the parent is transitioned to "In Development" when it is Approved, it doesn't need to be transitioned in the rule - it is the trigger for the rule to execute. The rule will look something like this: * Trigger: Issue Transitioned* To Status = In Development * Condition: Issue Fields Condition*…

Hi @Sreenadh The audit log is showing the reason for no action being performed is the Issue Key it finds - SDPD-1106 - is not passing the Condition (that the Issue be a Sub-task). Is SDPD-1106 not a Sub-task? If it isn't, the rule won't execute the Actions. --- Edit: It could also be depending on the Branch's settings.…

Hi @Mister Femi Yes it should - sorry about that! I've updated my response above, thank you for letting me know it was incorrect. Ste

Hi @Ingmar Heinrich I can see where you're coming from, and see the value of this suggestion. JAC is where Atlassian look at user requests though - if the idea isn't raised there, Atlassian might not know it has been (recently) requested. I'd still encourage you to do it, regardless of what the outcome might be :) Ste

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