John Funk Community Champion

Sorry, but the screenshot is now showing the projects in the Context. 

Yes, that's probably the route to go. 

I like all kinds of food! Mostly it depends on the mood I am in at the time. But I honestly think I could eat a freshly made and cooked hamburger everyday of the week. 

If I remember correctly, you like yours with extra pineapple. 

So that being the case, if it is only Project "Public" then the rule will only look at project roles on that project. 

Great! Glad it is working. 

That seems strange to me. Scrum at it's very nature has a WIP limit of one. Developers should not be working on multiple issues on a scrum board at one time. That seems more like an education issue than a board issue. 

So the rule runs against multiple projects? 

Hi Vera, You to grant the user access to the Jira Service Management product (must be a Site Admin to do this). Then add them to the Service Desk Team project role. 

Can you share the full rule? 

Go to the Custom Field and edit the Context to add the Project to the context for the custom field. Then come back to the List view, refresh it, and then it should show up. I see user picker fields in my list of custom fields for both the List view and Board and can select values. 

Hi Lena, What type of project is this? Company-managed? Team-managed? Business? 

So the Sub-task will get created as it is filled out. So for Edit Issue Summary field, put in the code: {{issue.parent.summary}} - {{issue.summary}}

You can't add another Condition? Can you share the actual rule that you have? 

Well, if I am reading all of that right in what you have presented, the only Condition you are using checks if the Issue is a Sub-task. You said it is, but the Audit Log says it isn't - so there's a disconnect there somewhere. 

You are not going to be able to put two values in the First Value field. You could create a variable using that calculation first, then use the variable name in the First Value field.

Happy to help!

Hi Sharmila, I suspect the Context is what is preventing it from happening. Update the Context to include the Project and Issue Type if that exists in the Context. 

So can't you just a condition for Project = ABC?

Hi @GCC Consultants - Welcome to the Atlassian Community! It is the UNIQUE set of Atlassian users in your instance. If all 150 Jira Software Users are also Confluence Users and JSM Agents, then that's your total. But if any of the Confluence users or Agents do not have a JSW license, then you need to add those people on…

So what does the Audit Log say? Is the Condition being met? 

Hi Izzy, Can you share the actual rule that you have now, showing the details of the field for the calculation? Also, try adding some log actions to that will show you the value after to select it to be sure it is returning the values you expect it to. 

Hi Swaroop, I assume your Queue is based on a JQL query. You should be able to create an automation rule base on that query that can then be used to email a group. 

Hi Daniel, No, there is no separate "create a board" permission apart from the global create shared objects permission. 

Thanks for the clarification. Maybe I am missing something or making it too simple, but what about something like below?

Hi Karolina, Yes, you should be able to do that. 

Yes, that is your problem. You can only have one value in the First Value field - so just {{lookupIssue.size}}

Hi Dishanki - Welcome to the Atlassian Community! You can set WIP Limits for columns on your Kanban board. This is the standard Kanban practice. When the WIP Limits are exceeded the column will turn red. It will not prevent the user from pulling too many cards to the column, but it will be very noticeable if they do. 

Hi Arno, Do you have a lot of custom fields? And do those custom fields have a Context that identifies specific project(s) used by that custom field? I used to get 500 errors all of the time until I added a context to all of my custom fields to identify the project and/or issue type using the Custom Field. 

Sorry for the late reply. Yes, that looks like some type of bug. I would open a support ticket with Atlassian to see if they can provide more info. https://support.atlassian.com/contact/#/