John Funk Community Champion

Hi @Wilson Seow I don't know if you ever got this fixed, but you should use [~accountid:{{issue.assignee.displayName}}]

Hi Vysakh, This can be done with the built in ProForma forms in Jira Service Management projects. Use the Sections to accomplish this. The following article should help guide you. https://support.atlassian.com/jira-service-management-cloud/docs/use-forms-in-jira-service-management/

Sure - you can definitely do that. 

@Craig Nodwell - You can look, but no touching. 

Welcome, Paul! And while you are at it - come give a follow in the New to Jira Work Management group. https://community.atlassian.com/t5/New-to-Jira-Work-Management/gh-p/newtojwm?

Since it's JSM, queues are one of the most used features. And that being the case, I find this one to be very helpful: * Queues for Jira Service Management

Sounds good!

Yes, at the end of the day, I just have to think that maybe I have provided another point of view not thought of already. And maybe that helps someone in the room to think a little deeper on the subject. And that brings me a sense of comfort. :-)

No, you can't do that in Jira Cloud out of the box. The closest you will come is with the Behaviours app by Adaptavist/ScriptRunner. 

Excelente! Fico feliz em ouvir isso.

Welcome Everyone!

The only thing I can think of to do is to name it in such as was as it is description for what it is. The length of the name doesn't really matter. 

It would still fire the rule, but it should fail at the Condition and not be successful. I would contact Atlassian Support to see what the rule still processed. Please post back here with the solution so we can close this one out for future readers. https://support.atlassian.com/contact/#/

And you thought my first response was an extended configuration? Good luck to you. 

Hi Sari, That's not possible. A user must have a Jira license in order to view a project in Jira. 

Limiting belief : Am I expressing something more from opinion or from fact? And is my opinion really any better than those that have already been expressed> Impact: This causes me not to speak up sometimes because I feel like I might just be adding noise to the conversation. 

Hi @samrat - Did you ever get this solved?

Hi Zoltan, Here is an article I wrote recently that you might find helpful. https://community.atlassian.com/t5/Jira-articles/Creating-a-Flexible-Recurring-Task-Issue/ba-p/2040862

Hi @Alena - Welcome to the Atlassian Community! If you do not have access to the issues because of the Issue Level Security, you will not be able to add information to them. 

Very good - let me know if you need anything else. 

Hi Hansika, I am not aware of a way to do that. 

@Robert Wen_Cprime_ - love me some Reece’s cups!!

So are you are using multiple fields by the same name of Approvers, with each having a context of a different project?

Correct - it would be in the Request Types - not the workflow itself. It should change the notifications, too, if it is hidden. Do you a quick test once set up to see. 

Glad you were able to figure it out. Sorry that I was not following what you were asking. I was concentrating on the step you have underlined in which the Approvers field is populated. I was thrown because there should have already been an Approvers field in your system after you got the Jira Service Management product. 

Hi Cesar, You can use a Cascading Field custom field type that might give you want you want. The first field has a dropdown with values. Then depending on which one you select, the next field has a specific list of values available for the value chosen in the first field. 

Ah, those are addicting, too!

Hi Gaurav, The closest you will be able to come I think is by using Groups within the portal. The Help Center is the top Level and then you could create multiple projects (and therefore multiple portals) under that, with groups inside each portal. But you won't be able to setup a streamlined hierarchy like that. 

Pretty much anything with chocolate. But especially Tootsie Rolls and Baby Ruth bars when I was younger.

Hi Rose - Welcome to the Atlassian Community! You can add another Condition to check in the first rule when the Sub-task is marked done. It might be that you add a custom field and then set the value in the new Sub-task when it is created in the second round. The field can be hidden from the screen. Then in the first rule,…