Aaron Williams Rising Star

Hey @Calvin Just to make sure I've understood. You have a number of external services, with different email addresses, that you'd like to set up in your desk to log incidents. And when these are logged you'd like them to be able to be sorted by automation to the correct queues? Thanks Aaron. 

Hey @[deleted] Looks like you've done a lot of great work already. I will try and tackle your questions and then give some suggestions. 1. You cannot have a default sub-task, but Jiras behaviour is to use the last sub-task type used. 2.If you remove the original sub-task issuetype, Jira will ask you to migrate the issues…

I would say that may require the use of some outside scripting or maybe the use of Scriptrunner to build the functionality. I image the feature to use the teams field in a form will be released some day. 

I'm not so great with HTML, so you may need to use some AI to help you out on that one. Unless someone here can chip in for you. 

Ah yeah, I missed that. But that being said the instructions I've outlined work for a cloud instance. 

You could try the advance compare condition, I believe that lets you use regex. Which you can compare against a smart value. Something like: First value: {{Issue.description}} Condition: contains regular expression Regular expression: *(animals1:dog|animals1:cat|animals1:horse) This is untested but give it a go. I always…

Hey @Mikel Whipple , At the minute it doesn't seem possible to directly call the Team field in a form. Out of interest how many teams do you have? It may be possible to do something via automation and a custom field but could get messy if you have hundreds of teams. Thanks Aaron. 

Hey @Rosana Casilli Are there any automation rules in your instance with a trigger "sprint completed"? It could be an automation rule causing the issue. Thanks Aaron. 

Ah, to keep things as they are on your end you could try wildcarding. Try description ~ "demo*" As this will match anything immediately after the word demo. As for your second point, the work item fields condition works the same as "demo*", so I would say it's personal preference. Let me know how you get on. Aaron. 

Hi @Julio Martinez Prieto Simply, you could look at the ticket history and count the times the status changes from there. You would be able to achieve this via custom fields and some kind of incremental count. And I'm sure there are an number of Atlassian marketplace apps. Each had their own drawback. Simply counting is…

To continue. It seems to be working fine for me. Using Work item fields condition Field: Description condition: Contains Value: Demo1 I have 4 tickets with Demo1 in the description and it finds all 4. Thanks Aaron. 

Hey @Kevin Williams Welcome to the community. There are a few quirks in Jira when trying to match text fields. So you may have found one. With this automation, trying to match text, it suggests something that will be occuring a lot. Is there a use case for this? Will Demo1 be the start of a common series of descriptions in…

Glad you have it sorted. Although it's not in your face you know now, make sure you share the knowledge 👍🏼 Have a great evening. 

That's great. So start with a schedule trigger and set it up in this way: Occurrence: Run rule every: 1 Days Pick a time that suits you. Check the box to run a JQL query And enter the following JQL: created <= startOfDay(-30) and status category not in (Done) This will capture all tickets they are 30 days or older and not…

Hey @Sandra Middleton I would set this up with a schedule trigger to make it super easy. Run it every day, at the beginning of the day. I can help design something for you, just a few questions. Is it for literally any ticket created 30 days or older? Or does status factor in to this? So ignore if say the ticket is…

Hey @Kevin Jamieson Welcome to the community. What method are you currently using to export the data? And is there a destination for it? This information will help narrow down what options we have to work with. Thanks Aaron. 

Hey @Rob Rudloff This article should help you out: https://support.atlassian.com/jira/kb/stop-ticket-creation-from-automatic-replies-in-jiradatacenter-and-server/ You need to edit the mail handler setting to ignore "Bulk" which looks for email with Auto-Submitted" and ignores it. Quick overview: Click cog top right >…

Hey @reza rouhafza Is this when you are using the incoming webhook action? 

Hey @Paul Singh Could you share some screenshots of your automation? Would be interesting to see it, as it'll help troubleshoot the issue. Seems like you've done a lot of work on it already. But one error in your logic is that the smart value only looks at the status category ie "to do" "in progress" "done". It doesn't…

Hi @nida ergenç Are you saying you wish the items you created from the action button become a child item of the issue you trigger them from? Thanks Aaron. 

Hey @Nitin Agrawal I have something working for you. I have created a custom field, which is a "label" type, I called it "SST: Previous Sprints" Here is the basis of the automation: Trigger: when sprint finishes. (Pick your board) Branch for each: Issues in sprint JQL IF: status != "Done" (pick your resolved statuses)…

Hi @Ahsan Raza This article will explain the permission you need to import issues: https://support.atlassian.com/jira/kb/permission-needed-for-csv-bulk-import-without-giving-org-admin-permissions-to-users/ Thanks Aaron. 

Hi @Ahsan Raza I will test some user accounts today, admin v non admin to confirm this for you. Thanks. 

Hey @Ahsan Raza From what I can see, you do need to be an administrator to perform this task. If you have the CSV all set up, could an admin on your clients side do the import?

Hey @Suzi Yousif What happens when you click the "contact support" link?

Hi @Nitin Agrawal There may be a couple of ways to achieve this. 1. Use Jira automation to write the sprint name to a custom field (maybe a label type field) 2. Use automation to write a comment to the story to log a previous sprint the issue has been in. Do either of those work for you? As I could help create the…

I just readded the epic issuetype to my board and the option did not reappear. I created a new epic, and the option did not reappear. Once I gave and issue the epic as it's parent the option returned again. Try creating a new test epic and assigning it an issue see if they kicks something into gear. Probably won't work but…

Hey @Axel Love MOUELE I would recommend messaging their support team, as it seems like it could be an issue their side. Here you go: support@getxray.app You may have an option to contact the directly through the app in Jira too. Thanks Aaron. 

Hey @C_ Byrer That is a very detailed question, and I can feel your pain through it 🤣. So I just had a play around on my free instance to test it. And found something to really simplify this for you. Users with the global permission for "Browse users and groups" will allow users to @ anyone with the same permission in any…

Hey @Papastefanou Have you tried simplifying your JSON to begin with? Raise a very simple ticket with just the basics filled out? Something like { "fields": { "project": { "key": "insert_project_key" }, "issuetype": { "name": "Task" }, "summary": "Brief summary of the task", "description": "This is the detailed description…