Aaron Williams Rising Star

Hey @Marcelo Gomes I'm also on the free plan and the option is there for me: Interestingly I removed the Epic work type from my project and the option disappeared. So you may want to check the work types in your project to make sure that hasn't happend. Thanks Aaron.

Hey @Grant Kessler I am assuming you've checked places like spam? If you can't find it at all, is there may be a chance it's being blocked by your organisation? Thanks Aaron. 

Hi @akilandeswari.ramadoss I think I've achieved what you need. Using the issue lookup action and then the {{#lookupIssues}} smart value. You can adapt the automation to fit your needs but as you can see from the output it does as you want. Thanks Aaron

I've tried trigger this via API and unfortunately it just copies everything as plain text. I think I needs to be triggered in a certain way which the API doesn't allow. 

That does help. I think this can be solved with an "issue lookup" action. You should be able to loop through them using the issue lookup loop function. I will test this for you later on today and if I get that bit working will send the structure your way. Thanks Aaron. 

Ah ok. You won't be able to add checkboxes into the ticket description, it only accepts rich text. The native Jira solution is subtasks, although you've mentioned you'd prefer not to use them. To achieve what you need you would need to look at the checklist market place app, but there is a cost associated with this. Thanks…

@Deric Ramsey I think that is the link @Pallavi Shirodkar shared: https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/ You'll see the section on creating your API token, I'm Atlassian would state here if you could create it via API if it were possible. 

Hi @Deric Ramsey I'm fairly sure you cannot get API tokens via the rest API. You can only create them manually. Thanks Aaron. 

Hi @Michael Remijan It is possible to call "Epic colour" = red, in a JQL statement but you have to use the colour codes mentioned here: https://support.atlassian.com/jira/kb/use-epic-color-for-epics-in-jira-cloud/ Let me know if you need any more help on this. Thanks Aaron. 

Hi @akilandeswari.ramadoss Just to make sure I'm clear. You want a manually triggered automation, that takes any issues that are in the statuses "in progress" or "done". This bit I understand but I have a few questions. Who do you want the results emailed to? The user who triggers the rule? And aids from the status do you…

Hey @Leoš MAREK Do you mean you wish to take the result of a check box and add it to a ticket description as a line of text? Say you have checkbox 1, checkbox 2 and checkbox 3 And checkbox 2 was selected. Via API you'd like a ticket that has "checkbox 2" in the description. Is that correct? Thanks Aaron. 

Very welcome, thanks for the idea though. Will come in very handy for our companies instance. Thanks. Aaron. 

@İclal Aslan I am unable to check your instance name. But it will be in the URL before atlassian.net/ You then need to set up the authorisation like so using your "Basic email:API key" the email and API should be encoded for security. 

Hi @İclal Aslan I think I have managed to achieve this using only automation for Jira. If you go to the global automation section and set the following Trigger: Project created Then: Send web request with this…

Well, I really like this idea and it seems achievable. I will work on this tomorrow as I see some value for our instance too. If I get it working I will share some screenshots with you. I will try and achieve the entire process within automation for Jira though, I always like to exhaust Jiras tools before looking at 3rd…

Hey @Izan Romera Almansa Could you tell me a little more about the customers in your instance? Do you allow customers to create their own accounts? Do you use managed accounts for customers? One of the issues you mentioned about an avatar changing colour is usually indicative of the account being different. Picking a user…

Hi @Nguyễn Phùng An If you know that project definitely exists, this error usually points to a license / permission setting. Are you the site owner? Did you create the project? Thanks Aaron. 

Hi @İclal Aslan This is a very interesting idea, and I can see great value in it for a customer needed to request access to a specific project or multiple projects. Have you started to create this? Or do you need help to see if this is achievable? Thanks Aaron. 

Hi @Elango_E You will need to use the REST API to complete this action. There is more information here: https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-organization/#api-rest-servicedeskapi-organization-post This allows you to create an Organization. If you create an automation with the trigger:…

Hey @AgileHappyLearner This is very possible, you would use "work item created" as the trigger and then a series of IF/Elses to go through all the possible outcomes, with an action to move the ticket in each. For example : When work item created > if custom field = "X" > then clone work item to "project X" Else if custom…

Hey @Heather Nygaard As @John Funk says, if you have created a form for ticket creation, users will need to use the portal. The create button will just display any fields that are on the screen it is linked too. Thanks Aaron. 

Hey @tasneem salille Can we have a little more information? Do you own the site? Or just invited to view the project? Any extra context would be really helpful. Thanks Aaron. 

Hi @Gopikrishna_Kunduru Is there a reason this needs to happen on the create screen? As far as I can see you can set up a couple of simple automations to achieve what you need. 1. When issue created > IF assignee "X" > Edit field Business role. This will assign the role on creation of the work item. 2. When issue updated >…

@Carlos Blanco This is the section to change the portal name, but remember to head to the bottom of the page as I think there is a save button. Please let me know if this helps Thanks Aaron. 

Hey @Yuly Buenahora The conditional fields feature in forms has been available form some time. It is done by adding sections to a form, and setting visibility when a drop down of your choice is selected previously. It's a bit limited, as you can only choose a single field per section to trigger visibility but it does a…

Hey @Akshay Ashokrao Kirmirwar Are you sure you aren't able to change this yourself? Your Job Title is synced from your identify provider, if your company uses synced accounts. Thanks Aaron. 

Hey @Jason Guzman As @Marc -Devoteam- mentioned it's easier for help when there is more detail, especially when dealing with automations. It sounds like you don't have the automation set up yet, but I would consider splitting this into two automations. 1. Assign the ticket on create 2.Re-Assign the ticket when a member of…

Thanks for that. So you are saying actions that are not "Pull request created" are triggering this rule? Have you checked the audit log of this rule? To see where the trigger is coming from?

Hey @Lauren Christianson Are you able to add scree shots of the automation you have set up? It'll really help when it comes to troubleshooting your issue. Thanks Aaron. 

Hey @Jaime Perez Shared configurations, workflows etc are exclusive to Company-Managed projects only. Team-Managed projects cannot share any of their configurations. If you'd like a clone of the project in question you would need to create a new project and set it up in the same way. Thanks Aaron.