John Funk Community Champion

@Aishwarya Parthasarathy - Next-gen projects have been re-branded to Team-managed projects. 

I would check the Fix Version field to make sure something is not getting stuck in there. But glad it is up and running for you!

Sounds like someone else keeps placing it there. You might want to check around. But that's the only way you are going to be able to keep it from being mandatory. The other option is to create a separate screen for your project if it is being used in a shared environment. 

Hi Arcolia, You will need to go to Settings (gear icon) > Issues > Priorities to make the change. You will need to be a Jira Administrator to do that, and it will have a global impact. 

Hi Arcolia - If I am correct, changing the value will just result in a new value being added. If both enhancement and Enhancement already exist, then you can make the change with no problem. But if you change from enhancement to Enhancement, there's a good chance you will end of up with both anyways. 

Hi Lesley, Your suspicions are correct - you can't just sort by the one value. We have added a custom field called priority number and sort on that sometimes. The problem is that once you sort on a field and not by Rank, you will no longer be able to drag cards up and down to reorder them. 

Hi Chris, The Resolution field was probably just added to the Create screen. Remove it from the screen and that should do the trick. 

The one thing I remember from my 30th birthday was receiving a simple button to wear that said 30 Hurts Enough said. 

Ghazal and Robert - It is always better to create a new question as many more people will see it. Also, each situation is often different and the solution might be different. Only people on this thread will see your message. I suggest you create a new question to get assistance.

That's very strange. Is the user in different fields on the ticket? Like maybe as the Assignee or Reporter on one but not the other? What field are you using to identify the user as an Approver? And is their name in that field? 

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

I'm like PJ - once you get to my age, you would rather stop counting the years. :-) No favorite one really stands out - there are the "biggies" like 30, 40, 50, etc. But I wouldn't say they were favorites! So now out tradition is the birthday person gets to pick the restaurant of their choice for a meal. That way I am…

Yes, that's exactly what I am saying. :-)

Ah, these are Team-managed custom fields. Therefore, you cannot get to them in the path I outlined as that is for Company-managed, shared custom fields. Your best bet is to just use the exact name of the custom field (including case) instead of the ID. So it would look like: {{#=}}{{issue.Total}}-{{issue.Actual}}{{/}}

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

Hello and Welcome, Bhushan! We are glad you are here!!

Hello and Welcome, Vivek! We are glad you are here!!

Hello and Welcome, Ahmad! We are glad you are here!!

Hi Adrian - Welcome to the Atlassian Community! If an approver can see some tickets and not others there must be something different about the permission schemes used by the projects. Are the tickets on the same project? Are they different issue types?

Hi Rob, Changing the Icon will affect all projects globally. You can have different Issue Types with different icons. But not the same different icons with the same issue type. 

My father instilled in me the virtue of working hard to provide for your family. He did this way more by his example than his words. He taught Horticulture at the local university and always had a love for gardening and flowers. Our family even owned a florist shop and greenhouses for a while. So I can say that I got my…

Great!

USA is July 4th

Hi ABC - Welcome to the Atlassian Community! For Jira Cloud, follow this guidance: https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/

Hi Pete, Try Project = ABC and duedate <= startOfDay(-7) and statusCategory != Done

Hi Ariane, Is there a sub-filter attached to the board (it would be near the bottom of the board settings general screen)? Can you provide a screenshot of that area? 

Hi @Jeevaranjan - Welcome to the Atlassian Community! No, that is not possible without the Schedule Issue permission. 

Hi Jan, Yes, this is certainly possible. Make sure that the custom field uses a context that includes the task issue type and same project as the Epic. 

Hi Melina, Automation rules fire based on a trigger that happens. In this case it would be a trigger for Issue Linked. 

Okay, thank you for the additional information. No, you are not going to be able to copy the value over just by creating it that way as the custom field is not available during create. You can probably create an Automation rule that will fire and copy the value over the linked issue when a linked issue is added to the JSD…