John Funk Community Champion

Hi Simon - Welcome to the Atlassian Community! If I am reading the error correctly, you need to add some JQL to your Scheduled trigger. You can do the same as your Condition - and thereby would not even need the condition. 

Hi Suzanne, This could be caused by a couple of things. First, users must have the Schedule Issues permission in order to change the ranking of issues by dragging them up and down in a column or in the backlog. Second, if the board filter must include ORDER BY Rank at the end of the board filter query. If it is missing an…

Hi Nicolas, You can also use a third party app such as Revyz Data Manager for Jira which provides for full and granular backup and restore capabilities. Full transparency, I am an advisor for the app.…

Hi Nader - I don't see a connection for you in LinkedIn. Also, I need to know if the companies are using Jira Cloud? Jira Data Center? Jira Server? 

Hi Tauanna, Jira Work Management projects require that all persons using a Form to submit ticket must be a licensed user and must have Create Issues permission. Your Free account only has up to 10 users at no cost, so it's highly unlikely that is what you are looking for. However, you might investigate the Jira Service…

You are welcome!

De nada

Hi @helpdesk - Welcome to the Atlassian Community! Yes, you can always upgrade again in the future. 

What type of field is the Client Name? Text? Or User field? 

Hi Hamza - Welcome to the Atlassian Community! When do you want to send the email? That will determine the type of Automation Rule trigger gets created. 

Olá Ale, Há uma ferramenta integrada gratuita para migrar projetos Asana para Jira Work Management. Você pode encontrá-lo em Projetos > Criar Projeto > Jira Work Management. Em seguida, clique no link Importar dados para um novo projeto. Você pode encontrar mais informações aqui:…

The vendor who makes the Rich Filters app. You can find that if you go under Manage Apps. 

Hi Bhanu, Atlassian Access only applies to users inside your domain(s) and have active accounts to access Atlassian products. But it applies to ALL Atlassian products - it can't be separated out to just handle Confluence or just Jira, etc. 

Hi Iris - Welcome to the Atlassian Community! What field are you wanting to Group By? The Filter Results gadget will not do a group by function either. Depending on the field, you would need to use the Issue Statistics gadget. 

It appears from your rule that you have multiple branches that keep progressing the status of the issue. Why are you doing that and not just setting the value to a single status? Why so many branches doing so many different Statuses? They are all firing and passing and keep moving the issue. 

Hi JD, You might try creating a custom field - just a radio button with a Yes/No or a Checklist with just Yes. Then when the issue moves to that status for the first time, set the value to use. You should be able to hide the custom field from the screen. Then you can check with your automation as to whether that field has…

Hi River - Welcome to the Atlassian Community! Try the Deep Clone app in the Atlassian Marketplace. 

Can you share the rule that you have? Also, be sure to publish your workflow, and then refresh the automation rules page so they will show up. 

Hi @이연주 - Welcome to the Atlassian Community! The error message says you are missing the Summary field. Is that field in your CSV file? Is it mapped correctly when doing the import? 

Hey @Matthew Nagel You should open a support ticket with Atlassian to find out what is going on. I see the same thing you do. Please post back here with the resolution. https://support.atlassian.com/contact/#/

Hi Marc, Right now there is not a way. You can vote for the request and follow it here: https://jira.atlassian.com/browse/JRACLOUD-41506

Hi @Aflog Tech Components are not available for Team-managed projects. You can vote for the request and follow it here: https://jira.atlassian.com/browse/JSWCLOUD-17601

Hi Eric, This seems to be very straightforward and doable. You would create a workflow with each of those statuses in a linear fashion. Then create automation rules for Issue Transitioned trigger for each status that the issue transitions to - one rule per status. In that rule you can assign the issue and email the user.…

Hi Trentin, You can edit the workflow and place a Validator on the transition to the status you want it to be required for before going to that status. Use the Field Required validator. 

Thanks for sharing! I have not seen that notice yet. 

I am pretty sure that is adding Customers to the Organization and not just inviting new Users. I would say give it a try and see what it does..

Thanks @Andy Heinzer !!

Hi Jen, You will need to open a support ticket with Atlassian to see if the user's email has ended up on the suppression list. https://support.atlassian.com/contact/#/

Hi Berik, You can create a project based on an existing project, so that one can be your test project. * Click on the Projects menu option in the top nav bar. Then select Create Project. * Next choose Service Management on the left. * Choose one of the templates. * Click Create Blank Project * Fill in the fields with…

Did you try the board?