John Funk Community Champion

Hi Christian - Welcome to the Atlassian Community! Yes, you can do that with an automation rule. Create a rule based on an Issue Created trigger. Add any conditions needed to specify only the issues that this update should happen to. Then add an action for Edit Issue. In the Summary field box put in smart values like:…

Thank you -that's much better. Just also remember that you are here to help others by providing good answers to solve their need, not just to promote your product. :-)

Hi Mirela, See if this article helps you. https://support.atlassian.com/jira-software-cloud/docs/create-a-cross-project-release-in-advanced-roadmaps/

Hi Gabe - Welcome to the Atlassian Community! There's not really anything built in Jira that simple. Here is an article that describes how to do an approval by email, but you should be able to get the gist of it to modify the process for other things.…

Hi @Andrea Rákosfalvy _META-INF_ - Are you associated with the app you are promoting? If so, there are clear guidelines that must be followed, including identifying who you work for and that you are connected to the app you are promoting. Let me know if you would like for me to post the rules here. 

¿Puedes proporcionar una captura de pantalla? Tengo problemas para visualizar lo que estás describiendo.

Asegúrese de que no haya ningún filtro rápido u otro filtro colocado en el tablero.

Just being a good listener and acknowledging people goes a long way. 

Congrats to my buddy @Brittany Joiner !! So well deserved!!

@gruposwa - É melhor criar uma nova pergunta para que seu cenário específico possa ser discutido. E mais pessoas verão sua postagem e poderão ajudar.

Yes, you can change the name so that the functionality stays at that level. You can change the name of the Epic to Feature and then create a new Issue Type and call it Epic and place it at level 2. This is Atlassian's recommendation. 

Welcome, Rishabh!! We are glad you are here!

Hi Richard - How many custom fields do you have? And do all of them have a context (or the vast majority of them) with at least one Project and/or Issue Type? Meaning the majority are not all Global custom fields. 

Thanks for sharing that - it really helps me to understand. And I think the path you have chosen to go is a good one. 

You will probably need to get Atlassian involved to help clean that up. Try one more thing though - when on a board, right click on the card and choose Add flag. Does it let you select the type there? If not, go ahead and open a support ticket with Atlassian: https://support.atlassian.com/contact/#/

The Parent should be a Key like ABC=123, not the ID. Can you post a screenshot of the first row of your CSV, along with the header row? Also, can you post a screenshot of the mappings in the import tool?

No, Issue Key is correct. Maybe it thinks you are clearing the Parent field for some reason since it is not mapped. So I try adding the Parent column in with the existing value of the Key for the parent. 

Hi Cédric - Welcome to the Atlassian Community! Not sure that I completely follow you, but it sounds like if you are looking at the screen for issue QUAL-93 there is a value for the field. But when you run a filter for that same issue, there is a different value in that field. Is that what you are saying? 

Oh, sorry, yes you do not need the Issue Type field either since these are just updates and not creates. 

Yay!!

Hi Kubeka - Welcome to the Atlassian Community! Can you share a screen shot of the whole board? Because that sounds like a Scrum board, not a Kanban board. 

Hi Steve - Welcome to the Atlassian Community! What are the steps you are doing to start the Import? What kind of project are you importing into?

Hi Rajat, This would be done with the Permission Scheme and Project Roles. Add users to the project in the People section under Project Settings. Assign the users one or more roles. Then modify the Permission Scheme for the project (it should be a non-shared scheme) to use the Project Roles you have just populated. 

Okay - you shouldn't need the parent if you are just updating field for the Sub-task. Put the key of the sub-task in the Issue Key field. Leave off the Issue ID and Parent fields - you should not need them.

Hi Nihar - Welcome to the Atlassian Community! Here is how you can transition to the Free plan. https://community.atlassian.com/t5/Jira-Software-articles/How-to-Downgrade-Jira-Software-from-Standard-to-Free/ba-p/2045188

You cannot create a second board IN a team-managed project. But you can do exactly what I said and it serves the purpose. The users have access and can click on the link in the left hand side just as easily has clicking on the drop down for the boards and selecting a different board. If back, it is one less click. Your…

Great! Glad to hear. 

You should probably go ahead and open a support ticket with Atlassian. https://support.atlassian.com/contact/#/ Please post back here with the resolution. 

Hi Barry - Welcome to the Atlassian Community! The advice might be related to the Server or Data Center version and might not be possible in Cloud. Do you have a source for the advice?

Hi Scott - Welcome to the Atlassian Community! It's probably best that you go ahead and open a support ticket with Atlassian here: https://support.atlassian.com/contact/#/