John Funk Community Champion

G'day Yannick - is that not your form? 

@katharina.rott - My understanding is that they will try to update your rule for you automatically when this rolls out to switch out the Summary for the Epic Name in your automation. But they also have given the caveat of that might not actually happen. And it won't look like issue.Epic.Summary. It will just be…

Can you share a screenshot of the message they receive? 

Okay, that's a different story then. You will need to do a migration for sure. You should be able to Google that and find a path to take. 

Hi @Sunilkumar k I am not sure of the actually process of board migration, but if you mean just the board itself (and not the cards on the board) then it is very easy and fast to recreate the board in Cloud. Simply create a new board based on whether it is Scrum or Kanban. This board can be based on an existing project or…

You still need to check the Permission Scheme used by that project. You can run the Permissions Helper while you are there to identify exactly why they can't see the Browse Projects permission. 

Hi Pasam, I don't know that you can prevent that from happening, but you can become aware of it by Approving your Domain. From admin.atlassian.com go to Products > User access settings > Add domain. Then if someone creates an instance with an email from that domain, it will show up in your admin.atlassian.com tool under…

Hi @CHINNAMUTHEVISAI.SATYANARAYANASHARMA Access to projects and issues is all done with the Permission Scheme attached to the project. Just because you are a Jira Admin does not automatically give you full access to everything. You still must be in the Permission Scheme in some way. If the intent is for Jira Admins to be…

Hi Ninad, There's a couple of ways to approach this. One is to manually do a move from one project to another. There is no automation capable of doing that. The second is to create an automation rule that will clone the request into another project, or create a new issue from scratch in the other project. This is actually…

Hi Zaldy, Actually both of those syntax should work. Can you share the actual rule with the details of where this is placed in the automation? And the results of the automation (output)?

Hi Ankit, It depends on the time of day when the issue was created as to which query will display the issue. I would use: created >= startOfDay(-1) and statusCategory != Done and issuetype in (Bug, Incident) and priority in (High, Urgent) 

Your screen shots all show for Atlassian Access. Is that the only product you are using? Click on the Products menu in the top nav bar to see what is is loaded and might need to be paid. 

Hi Diksha - Welcome to the Atlassian Community! You will need to open a support ticket with Atlassian. Use the option for Billing, Payments, and Pricing. https://support.atlassian.com/contact/#/

Happy to try to help. Please post any resolution back here that Atlassian might provide for future readers of the post. Good luck!

I apologize for forgetting to include that! https://support.atlassian.com/jira-software-cloud/docs/create-and-add-teams-in-advanced-roadmaps/ There are probably better links somewhere out there, but that was the quickest I could find. My understanding is that the people included in the Team would be Jira users in your…

Hey Tim - Welcome to the Atlassian Community! Atlassian is aware of the issue, and I believe they are working on it. This is a related one that you might want to vote for and follow: https://jira.atlassian.com/browse/JWMCLOUD-173

Hi Dave, These are actually Teams and not Groups. You can read more about it here. But basically, anyone with a Jira license can create a Team and add people to it. Then that field can be used to tag people in the Team as you have noticed. Pretty much anyone can tag any Team in a comment. 

@Phil Bustin - so what's different about not having the 7th option that needs to change what you have so far? And can you share the rule and what's missing with the functionality that you want? 

Good point about the youth 

Hi Nadica - I know this is very old, but did you ever get a solution? I don't think you will be able to have the tab highlighted, and it's probably best to use a Transition Screen on the transition if you are making a field required at the time of the transition. But you may have already done that. 

@Дилноза Улугбекова Есть новости по этому поводу? Вы нашли решение?

Hey Rob, A few things - Jira Core is the base level Jira product. That's what Business projects are. So everything is built on top of that - for instance Jira Software, Jira Service Management, etc. But that doesn't explain why they would force you to change the project type. However, I see that you have a Free instance,…

Great! I thought that might solve it. 

Hola Fidias - ¡Bienvenido a la Comunidad de Atlassian! ¿Qué tipo de categoría es Listo? ¿Está hecho, por hacer o en progreso? Puede intentar usar statusCategory != Done en lugar de solo estado ("Status").

Oh - not sure then as I don't have a DC version. @Bill Sheboy - any thoughts? 

Yes, I will be interested to know what you find out. When I test it here, it opens the form for me to fill out when I click the Create button. 

Labels are used for one or two word labels. Curious where you got that definition of Epic Name - that might just be something local that has been decided how you are implementing that. My point is that is just seems useless or redundant to me. And it's mandatory which makes it a stumbling block. If it wasn't required, I…

Oh, so they are creating the issue outside of using the portal and you want to force the user to use the portal view with the form. Correct? Inside the form when editing, go to the Settings tab. Click on the option for Create new issue. 

Hi Yannick - Welcome to the Atlassian Community! Go to Project Settings > Forms. You can create a Form there. 

Glad you got it working.