Jack Brickey Expert

You could simply add a label and default sort to have the ”warning” issues first. 

Does the project have a Project admin? They may be changing. 

Hi @Rokas ,, there isn’t a highlight but you could consider a separate queue or consider a custom field that could be set via automation. The best (?) solution would be driven by your use case details. 

Yes indeed. Let us know the results

Did you start typing in the desired org?

Good point Bill. I did not come back to that point after seeing the error message. It will be good to understand the webhook requirement. 

Hi @Cynthia Pearson , there are quite a few posts in the Community on this. Basically you would set up an automation rule that would run every day using a JQL. Any issues found by that JQL could then be actioned by an email. In fact I just checked the Templates area under automation and found this.

Hi @Drishti Maharaj , in your action component please select the "organization" field. You should be able to then include the organization that you desire. The request participants field would be for individual customers.

Correct. 

Hi @Gal Fatal , sorry for the delay in getting back to you. I have been off on other errands. I would like to test a theory out and was wondering if you could either clone or reconstruct that rule from scratch and see if that error message persists.

Hi @Santhosh Raj , you can vote for this issue if you like - https://jira.atlassian.com/browse/JSDCLOUD-9024 

Thanks Gal, the details help. For your Manually triggered rule can you check to see if the Actor is set to "user who triggered the event".

Ugh....that should never be done especially if the workflow is a default workflow. 😣

Ok, a bit stuck on what might be going on so can you share a few screenshots: * where you are creating an issue and setting the priority * viewing the issue as soon as it is created * history tab view also, I assume if you change the priority after created it persists?

Got it thanks. So have you tried a different browser? Does this occur for all dashboards? You might need to report to Atlassian.

Hi @Sadaf Maqbool , the Community is a great place to find or present answers to questions about Atlassian products. You can also join groups to engage with others on various topics of interest. 

Hi @Yevhenii Tym , what do you mean exactly? Can you share a screenshot illustrating your issue?

Please reference this suggestion- https://jira.atlassian.com/browse/JSDCLOUD-10697 

Smartvalue cannot reference a Form value unless that form field is associated to a Custom field in which case you would reference the custom field in your smartvalue.

Can you provide a screenshot of the view all issues screen using that JQL

There is a default generally selected for priority but that simply chooses the priority if one is not selected. So there are no automation rules then?

hi @Marvellous , the customer should receive an email assuming you have Customer notifications set - project settings > customer notifications > public comment added. As an agent you can add a public comment either by replying to the issue created email or within the app. The customer can also access the Portal to view the…

Have you check the history tab to see if the field is being changed? It could be an automation rule.

Hi @Fares Laroui_Vectors_ , I assume you mean that certain text in a comment would result in a certain label? If so, have you consider using automation to inspect the comment made and if it meets certain criteria then add a label?

Oh, one comment here. You mention "I try to use the {{initiator}} smart value to retreive the initiator of the issue...",but to be clear {{initiator}} refers to the user triggering the rule not the reporter of the issue for which you would use {{issue.reporter}}.

Hi @Gal Fatal , I wonder if it is related to the ongoing issues with Automation. https://jira-software.status.atlassian.com/ 

You should try using the custom field ID which you can find ate the end of the URL when editing the custom field. Here is an example... https://xxxxxxx.atlassian.net/secure/admin/EditCustomField!default.jspa?id=10089 then you reference as follows... {{issue.customfield_10089.accountId}}

I would suggest opening a support request with Atlassian.

are you the organizations admin? If so, have you inspected the users under user management? That is where I would start and if necessary reset the password.

Hi @Office , I concur that this would be useful. I found the below closed Suggestion that has a "timed out" resolution. You might consider either using the in-app feedback link or open a support ticket with Atlassian to provide your input. https://jira.atlassian.com/browse/JSDCLOUD-5486