John Funk Community Champion

I suspect the error is because of the parentheses used in the name of the field. Try using issue.customfield_16754 where that number is the id of the custom field instead of using the actual field names. So, something like: {{issue.customfield_16754}}, {{issue.customfield_15732}}

Привет @Razmik Mikayelyan, Я не понимаю вашего вопроса. Запрос работает не так, как вы ожидаете? Если нет, то что он делает такого, чего не должен?

Hi Ayesha, Try just using issue. instead of triggerissue.

You were able to add other values at one point, but then the field was locked down and now you can't. That happened a few years ago. 

Hi @mjaglan - Welcome to the Atlassian Community! Yes, you can run a query using JQL (i.e. a filter) and then do a Bulk change to add yourself as a Watcher to every issue returned by the query. Then you can create an Automation Rule for an Issue Created trigger that sets you as the Watcher for all new ones. 

:-)

It would be an add-on for Server. There is a free version called Automation for Jira Lite, and a paid version called Automation for Jira Pro.

If it makes you feel any better, they do have a group working on this. But I don't know the timeframe. 

I have nothing additional for syncing multiple instances that the add-ons mentioned by others in this thread. I have not used them, but they are very good tools from what I understand. 

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

Hi Aleksander, Yeah, that frustrates me, too. It's usually due to there not being an already existing outflow from the status that you are adjusting. The only solution is to copy the workflow, make the changes to the inactive copy, then add the new workflow into the existing workflow scheme to replace the existing…

Hi Kerry - Welcome to the Atlassian Community! Can you provide more exact information as to what you are trying to do? 

What is the filter used by the board?

Hi Rutu - Welcome to the Atlassian Community! What type of project are you using? Company-managed? Team-managed? Jira Work Management? What is the filter used by the board? 

I still Youtube for various music as well. :-)

Agreed - you need to quit using Epic Name and concentrate on the Summary and Epic Name will be going away soon as Bill says. 

Hi Pier, There is no concept of archiving issue types in Jira. You must migrate issues to an existing issue type if you plan to delete one of your issue types or remove it from the issue type scheme. 

Hi Qu - Welcome to the Atlassian Community! It sounds like he hasn't accepted the invitation. Are positive he has already logged in with that that same email address? 

Well, that's because there are multiple comments that can be linked to a single issue. It would have to know which comments. 

Hey Scott, I just added the Activity Stream gadget to my dashboard with no problem. 

Hi @Mick C - Are you still needing help with this?

Hi Patricia - Welcome to the Atlassian Community! Do all of the emails end with .com? 

I would add the log action before the Edit Issue fields step. And capture the initiator. 

Hi Caglad, What do you have so far? Can you share a screenshot? And what is not working with it? 

Hi Kiranmai, Can you share a screenshot that shows the entire issue - most notably at the top?

Hi Daniel - Welcome to the Atlassian Community! What are you trying to achieve with the rank? I really doesn't make a lot of sense in relation to JQL. 

Hi Dylan - Welcome to the Atlassian Community! Jira doesn't know when an issue is assigned if it is the first time or 20th time. So you need something else there to check it. Maybe try creating a new custom number field and set the default to 0. Then add another Condition to check if the value of the custom field is 0. If…

Hi Anna - Welcome to the Atlassian Community! Instead of choosing an option for the Epic Link, type this in: {{triggerissue.key}}

Maybe add some log actions to see what value is being set. 

Hi @Adam V. - Did you get this solved?