John Funk Community Champion

Hi Kevin, I would have a separate project for each team. Then you can create a single board for all of the projects worked on by that team. Then you can add quick filters by project to the board so that each team member can simple click on the filter for that project to hide the remaining fields. 

Thanks, David!

Hi Erica - Welcome to the Atlassian Community! There should not be a difference in the Issue Layout based on the user for issues in the same project. Is it possible there are different screens based on the issue type? 

You can learn more about that here: https://confluence.atlassian.com/adminjiracloud/configuring-issue-level-security-776636711.html

Hi @wahaj_afzal - Welcome to the Atlassian Community! Make sure the Labels field is on the Edit screen for that project. 

Can you post the board filter for the current board? But, yes, in general, you need to make sure the filter covers those issue. For those in particular, if needed, you could add AND "Epic Link" = ABC-123 and key = ABC-123 This would where the Epic you have is ABC-123. I hope that makes sense.

More of an HRIS than a CRM. Stores both meta data and creates annual tasks for leaders to complete annual reviews of each team member. Now that Insight is here, it probably would be a better approach!

Great glad it is working for you then. If this took care of it, can you click the Accept answer button above to close this one out? Thanks! .

When you click on Create Project, you should be able to see Jira Service Management as an option if it is installed. But bottom line is the workflow needs to be on a JSM project to have the approval show up. :-) If this answers the question for you, can you click on the Accept answer button above to close this one out?…

Hi Susan - Welcome to the Atlassian Community! First just a note that issues are not created against boards. They are created on projects. Boards use filters that determine which issues show on the board. So, having said that, you need to look at the filter associated with the board to determine the criteria for the issue…

Hi @Dede Eko Tya Sembodo - did you ever get this resolved? 

Hi Julie, That certainly looks like it should work. What does the audit log show for it? Does it say it passed the condition? Also, just curious, but why the check on the project? Shouldn't you just create the rule as a single project rule? 

Hi Nancy - Welcome to the Atlassian Community! You are not going to be able to lock down a single field by status by group. You could use issue level security to lock the entire issue from a group once it hits a particular status, but not just a field. 

Hi Eliot - Welcome to the Atlassian Community! Let's take these one at a time. And first - you will not be able to assign an issue to a Group - only to an individual. But you can assign the issue to an individual based on a round-round or random or a balanced work load. We will proceed assuming you want to do one of those.…

You are not going to be able to remove them - you can only replace them. .

Are you sure this is a JSM project? .

The steps in the workflow

Yep. :-) If this took care of your question, can you click on the Accept Answer button above? 

Hi @Agnieszka Santos Yes, you can do that by creating different Field Configurations for each issue type and then package them together under a Field Configuration Scheme. Then attach/replace the scheme for the project. 

Yes, you need to create a new workflow. 

Hola Pedro, Anteriormente, hubo un problema con los correos electrónicos enviados desde Automation for Jira. Eso debería aclararse ahora. No estoy seguro de si la automatización seguirá adelante y se ejecutará o si necesita ejecutarla manualmente haciendo clic en el botón Ejecutar regla.

You are welcome

I really enjoy being in the office. I don't like the commute, but the interactions with other humans is better for me and my marriage. :-) However, I would really enjoy one day WFH and the rest in the office each week. 

Use the Advanced Compare condition

Hi Deepika, There is an Advanced Compare condition in Automation for Jira that might provide what you need. Here is more information on Automation if you are not familiar with it: There are two types of automation: * Global: In the Free version, you get 100 executions per product, per month * Project: In all versions, you…

You would create a custom validator for that transition, but I am not a nunjucks expert and not sure of the syntax. @David Fischer could you help? 

Hi Antonino, You should copy the shared workflow and then make your changes to the new inactive workflow. Then you will probably want to copy the shared Workflow Scheme as well and change out the previous shared workflow for the new workflow you just created. Then attach the newly create Workflow Scheme to the project that…

Hi Calogero, You have 11808 in your search but the field is 11807. Also, will the text of the field not show up? If still no, you might try some JSON in the advanced section for the field. 

Hi @YTZ You should be able to do that with the Automation for Jira add-on. But I don't know the syntax for what that looks like using pure code. 

Oh, that's a little more complicated then. One way to to use a third party add-on like JMWE or ScriptRunner to check the value/size of the field to see if it is larger character wise. An out of the box solution might be to create another custom text field and populate it with the values of the Root Cause field when it gets…