John Funk Community Champion

Hi @liujingwuljw - Welcome to the Atlassian Community! No, you must be a Jira administrator to be able to modify issue security schemes.

That is very strange. What type of field is it?

Hi Rasajna, have them take themselves off from being watchers of the issue. Depending on your notification scheme, that should take care of it. But if they are watcher they will receive everything.

Hi Prajwal, No, the data will not be affected. You can switch back-and-forth as much as you like.

Hi Dace - Should also be immediate, but you have to refresh the automation rules page for it to show up. Be sure to save anything you’re working on now and publish it. And refresh the page and it should be available

You can manually pick for each column already - but it sounded like that is not what you wanted. It sounded like you wanted to set the order of each ticket for each column based on a recurring relationship. You can only do that by adding the ORDER BY to the filter. And you can't mix and match them - you can either do…

And can you post the audit log for when it runs? Also, you can click the blue button in your screenshot and have it run immediately. 

Great! Glad you are making progress. 

Simeon beat me to it! We always have an exterior app send the user’s email address. Then that works like a charm.

Hi @medjouti Can you share your actual rule? And what is not working? Is there an error? Does it run and does nothing? Does it not run? Please share the audit log for the rule, also. 

If the Notification Scheme does not list the field/person, they will not get the notification. If they are in the Notification Scheme, they should. You can test that using the Notification Helper tool inside the Notification Scheme. 

Hi Jonathan, The only way I know to do it is to get Jira Service Management and create your form there. Then you can hide a field (even Summary) and give it a predetermined value so the create will still happen. 

Hi @RGrimner - Welcome to the Atlassian Community! That sounds about right - I would not expect the mail handler to create multiple tickets from a single email. 

Hi Zaldy, It's actually the ID of the transition. It can be used in post functions and other such things when using add-ons like JMWE and ScriptRunner. 

Great! Glad it is working now. 

Hi Ahamad - Welcome to the Atlassian Community! This is probably because you don't have the permission needed to share filters. Your Jira Administrator will have to grant that. Allow users to share dashboards and filters with the public. ON

Hi Nikhil, Try {{issue.resolution.name}}

Hi @dbelouso Rank out of the box in Jira is very complicated. On a board, I am pretty sure it has something to do with when that ticket actually came onto the board. So even if you change the order in one column, when it is pulled into the next, then it puts it back in rank according to the original rank. About the only…

Hi Marina, You can create a new custom field of Paragraph type. Then edit the Contexts and Default Value for the field to add your table into the Default value field. You can change the renderer of the field to Wiki Style if you need that but changing it in the Field Configuration for the project. 

That's really cool! Who knew there would be a YouTube channel about that!

Great! Glad you got it working. 

Hi @Martin Fukatko - Did you ever get this resolved? 

Hi @Fabian Weber - Did you ever get this resolved?

Hi @Ivan Andrieiev - Did you ever get this resolved?

Hi @Chandni Gupta - Did you ever get this resolved? 

And what did the Notification Helper say? 

Sure - give that a try. 

Hi Ole - Welcome to the Atlassian Communiity! Do you have both projects listed in the Rule details for the rule? 

Welcome Ram! Create a test JWM project and check it out!

Thanks for the update. Hopefully, they will get a fix soon.