John Funk Community Champion

Hey @John McKiernan - can you bring any clarity to the custom fields for Next-gen not showing as available to copy to the Assignee field? @Joe Hankin - Isn't the Owner field a custom field? What's different about it than the other custom fields that aren't showing?

Hi Jurica - have you re-indexed since the name changes? 

Hi @aashish gupta , I do a check to see if the values of 5 fields add up to 100. If they don't then I send an email to a group of people. I do all of that with an Automation For Jira rule. Below is a screenshot of the rule. One note - Automation For Jira cannot prevent the user from doing things if it doesn't add up to…

Hey Joe - It's probably because the field is not available to either the project or the edit screen. Check the field Owner to see what is different about it because it is a custom field, too. 

Make sure the person has access to the system. Go to Settings > User Management and check the user's access. Can you send a screenshot of that? Also, on the project, make sure the user has permissions based on the Permission Scheme. You might need to add them to a role on the project. Go to Project Settings > People to see…

Hi @larias , If you switch over to the New Jira Issue View, it should pop up when you click on a card on a board. To change, click on your avatar in the top right corner of the screen. Then select Personal Settings. Then about halfway down toggle on the New Jira Issue View. Then hit your browser back button. 

Hi Julia - Welcome to the Atlassian Community! You might check to see if the user has permission to Create issues for the project. Also, since it is happening in both the admin and issue creation area, I would tend to think there is a web browser problem. Can you try with another browser or reboot your computer to see if…

Hey Chris - Yes, that's the behavior that has happened for as along has I have been using Jira Cloud. You could submit a request for clarification if you like: https://support.atlassian.com/contact/#/

Can you share a screenshot of that? It should look something like this:

Hello and Welcome @JiBrok ! We are glad you are here!!

Great! Glad it is working for you.

Hi Cathy, Yes, Epics can be linked to issues across multiple projects no matter what project the Epic was created against. 

I would just use Copy from Current Issue. Then click on the words Current Issue and that will give you a popup where you can select the QA Resource field. 

Try putting a new action for Re-fetch issue before the condition to see if that helps. If it still doesn't work, can you send a screenshot of the audit log? 

Hi @afsal nazar - I am confused as to why you added the second condition at all? If it doesn't match the first condition it will do nothing, which is what it sounds like why you are adding the second condition. What is not working in the first condition that would make you want to add the second condition?

Привет @Матвей ! Добро пожаловать в сообщество Atlassian! Убедитесь, что у пользователя нет разрешения «Редактировать проблемы» в схеме разрешений для проекта.

Hi Scott, Do you have a rule built already using Automation For Jira? If so, use the Edit Issue action and not Assign User action. Then Select Assignee and copy the value from another field. 

Hi Angela - Welcome to the Atlassian Community! Can you be more specific as t the error they receive? Maybe even a screenshot? Also, do they get the error the very first time they try to log in? 

That usually means that you are not a Jira Administrator and cannot modify the transitions on workflows. Is that the case?

Hi Holly - Welcome to the Atlassian Community! You will need to modify all other permission schemes so they don't give access to any groups that the 3 users may be in (like jira-users).

Unfortunately, no that's not possible. I would just limit who has the ability to create projects (they must be a Jira Administrator) and I would educate them. If they don't listen, the remove their permission to create. :-)

Hello and Welcome, Jerômine!! We are glad you are here!

Hi @rahuldanwade - Absolutely! Providing a context more specific than Global is certainly recommended for Cloud. 

Hi Jose - Welcome to the Atlassian Community! Have you tried refreshing the list of rules first? Sometimes it times out and is not obvious. So, refresh the page, then make a simple change and see if you can save it. Maybe something other than the Assignee. If that doesn't work, you should submit a support ticket to…

Since you mentioned Next-gen projects in the title of your question, that's what I sent to you. If you are looking for more generic descriptions of fields and their capabilities, you can see them in this article: https://confluence.atlassian.com/adminjiracloud/custom-fields-types-in-classic-projects-972327807.html

Hi Margarita - Welcome to the Atlassian Community! I would suggest you first get familiar with custom fields in Next-gen by review this article: https://support.atlassian.com/jira-software-cloud/docs/customize-an-issues-fields-in-next-gen-projects/

In that case, that looks like you need to submit a support ticket to Atlassian for a bug: :-) https://support.atlassian.com/contact/#/

Hi @Shpendi Rakipi , I have found that often when this happens that Atlassian has blacklisted the email address for some reason. I would submit a support ticket to Atlassian to make sure the email address of the user has not been blacklisted. https://support.atlassian.com/contact/#/ See if you can approve this anwser. :-)

Yes, you can always search on a field for a value. :-)

That is because this was created as a Discussion and not a Question. I will see if someone from Atlassian can move it over.