John Funk Community Champion

Hi Reno, After you create the new custom field or change the name, simply refresh your browser tab with the Automation rules. The field will immediately show up. 

My oldest son lives very close to Glacier National Park in Montana, USA. My wife and I went on a hike with him a few summers ago. It had been noted once we got on the trail that there had been bear activity in the area. We had no bear spray or really anyway to defend ourselves if we encountered anything. He kept telling us…

Hi Juliet - Welcome to the Atlassian Community! Can you provide more details? What do you mean by supposedly? Either it is or it isn't. Why is the notification being sent? And do whom? Reporter? Assignee? Etc. 

Hi Lilian - Welcome to the Atlassian Community! I assume you don't mean the ticket/issue key (like ABC-123) but the actual ID of the issue. If you run a query/filter and then export it to CSV (with default fields) you should see the ID as well as the Key. 

Привет @Евгений ! Добро пожаловать в сообщество Atlassian! Вам необходимо предоставить более подробную информацию, пожалуйста. Что именно ты делаешь? И какую ошибку вы получаете? И, пожалуйста, переведите все ошибки на английский, если это всего лишь скриншот.

Hi Mehak - Welcome to the Atlassian Community! You need to submit a support ticket to Atlassian to have them check if your email address is on the Suppression list. https://support.atlassian.com/contact/#/

Hi Slava - Welcome to the Atlassian Community! Make sure the Linked Issues field is on the create screen for the project and issue type.

Hi Adriian Are you actually in the group? You have to be in the group in order to use the group.

Hi Fahad, Unfortunately, no. You will need to create a new issue type at -1 and migrate the issues from the 0 level issue type to the new -1 one. And, of course, you will need to connect it to an existing parent. 

Hi Daniel - Welcome to the Atlassian Community! A simplest answer is to go to the issue and click on the history tab in the activity section at the bottom of the screen. There you can see in the history who moved it to Done and the exact time it was done.

Hi JK - Welcome to the Atlassian Community! You must be a Jira Admin to be able to add those. Go to Settings > Issues > Issue Types. If you do not see the Issues option then you don’t have that permission.

Hi Adriano, Make sure the board filter is shared with the user.

Hi Ribas, I think you are very confused. Workflows do not have attributes. You can have different workflows on a project but each workflow must be associated with a different issue type. You cannot have two workflows for the same Issue Type on a project. 

Hi Emilie - Welcome to the Atlassian Community! Check the Permission Scheme for the project to see who has the Assignable User permission. 

Hi Kel, First, you really should change the name of the field you added. That or add a second context that you can use different values for either different projects or different Issue Types. Regardless, to get the ID, go to Settings > Issues > Custom Fields Search for the Severity field. Click the 3 dots menu to the…

If you would be kind enough to click the accept answer button above, we can close this one out. Thanks!

Hi Steven, Unfortunately, I don't believe you are going to be able to lock that down or hide it. You should create a new custom field that you have more control over and use that. But you won't be able to do that at the Project level without some type of add on. 

Hi Sanyal, Yes, your licenses are not named user licenses, just a count. So make one user inactive and then you can add a new user. 

Good. So everything is good now with your hierarchy? 

Hi Fabrice, Yes, your licenses are not named user licenses, just a count. So make one user inactive and then you can add a new user. 

Hi RH, Notifications are based on a combination of the Customer Notifications for the Project and the Notifications Scheme for the project. Internal users are Agents on the project and External are non-Agents.

@Senthil Kumaran - Any update? 

Great! Glad it is all sorted. If you will click on the accept answer button above, we can close it out. Thanks!

It might be good, but it might also have been changed and saved several times before. So it looks like only Jira Admins will be able to make changes. You can open a support ticket with Atlassian if you want to pursue that further as they are the only ones who will be able to tell you really what is going on. 

No, because definition, the custom fields must be Global context to be used with Team-managed projects. 

Correct. I did that with about 25 Asana projects back in November.

Hi C S, Make sure above those that it says Any of the following conditions and not All of the following conditions. 

Hi Rosie, You need to open a support ticket with Atlassian and have them check the Suppression list for the email address. https://support.atlassian.com/contact/#/

Sure - it's simple. Edit the workflow. Click on the transition to the Done status (the line that goes to the Done status). Then in the popup on the right that shows up, click on Post functions. Then click on Add post function. Select Update Issue Field. Select the Resolution field. Then in the Field Value, select Done.…

Great - glad you got it sorted.