John Funk Community Champion

You can do a couple of things. One, you can click on the gear feedback link on the bottom left of the project and let Atlassian noYou can do a couple of things. One, you can click on the gear feedback link on the bottom left of the project and let Atlassian know that you want to have filters for Done items for Jira boards…

Sorry Roudy - I am not Atlassian and cannot do that. You need to submit a support ticket with them. And you should update your post to remove your email because the whole world can see it right now.

Hi Alexander - Welcome to the Atlassian Community! Can you share a link to the documentation? 

HI Mickey - Welcome to the Atlassian Community! Can you share a screenshot of the entire issue? 

And you are in the Administrators group? And you are in the Project Role Administrators? 

The point is that it doesn't matter with a Free version - everyone has access to everything. It doesn't matter which role you give them or don't give them - they are still treated as Administrators. 

Ah, es un proyecto gestionado por el equipo. Esos son diferentes. Atlassian está agregando un nuevo campo llamado Categoría a los nuevos problemas, pero aún no se ha implementado por completo.

Sí, mi captura de pantalla es de una versión gratuita.

Hola Jaime, la página Detalles del proyecto

Well, that all depends on how you are managing your business and the types of things that you are looking at the tool helping you with. Can you describe more details? 

Hola Pauline, Las reglas de automatización no funcionan así. Disparan DESPUÉS de que el evento haya ocurrido, no durante. Por lo tanto, no hay forma de autorelleno un campo durante el proceso de creación (es decir, cuando se muestra la pantalla de creación).

Hi Priya, After you copied the board and created a new filter. Did you change the filter out on the board from the old to the new? 

Hi Charlie - Welcome to the Atlassian Community! You need to add a Post Function to the workflow used by the project for the transition to Resolved status. There, be sure to set the Resolution field with a value. 

Ah, sorry, I was thinking of the description associated with the field. This is a little trickier for Company-managed projects because the Description field is shared across all of those types of projects. So if you put in a Default Value (which is where you would put it), then it will affect ALL Company-managed projects.…

Hi @pirtle - Did you get the webhook to work? 

See my earlier comment about changing the Field Configuration. :-)

Very interesting. Glad you found a way to make it work!

Hi Marcel, Check the shares on the board filter to see if you have access to that. 

Let me see if someone from Atlassian can come take a look at it. 

Does it have to run manually right then? What about a scheduled email once a day or more?

I don't know of a way to do that right off the top of my head. Other than hard coding the assignee like you have it and create a separate rule for each person. How many people are there? 

Hi Sara - Welcome to the Atlassian Community! There are still some issues with this working properly in my opinion. What I had to do was click on the > beside the Epic to "expand it", though nothing might happen. Then if you will drag the child up or down in the list, it should adjust and then show up under the expansion.…

Then maybe change it to ends with .com

Yeah, I think it is getting confused as to who the actual user is when the rule is fired, meaning the Actor. So even if Alex fires the manual trigger, it might run as the Actor of Automation for Jira. Does that make sense? 

Hi Uma - Welcome to the Atlassian Community! I would setup a Scheduled trigger automation rule that runs once a day. You would use JQL that looks like this: project = ABC and duedate = 5d Then you add an action for Send Email, and you would send it to the Assignee with information about the issue. 

Hi Alex - Welcome to the Atlassian Community! What is the trigger that causes the automation rule to fire? And who is the rule run as? 

Well, that's really weird. Is there any reason that the Assignee can't be set to the person who moved the card? And then maybe update the Tester field by copying it from the Assignee field. 

Hi Krishna - Welcome to the Atlassian Community! Did you publish the workflow after you changed it? Did you map the new status to the column on the Sprint board? 

Hi Nathan, You should be able to see those when you click on the status - they just can't be a button. 

As a Jira Administrator, I have not had an instance where I could not update a Permission Scheme. Can you get to the People section of the Project Settings? And if so, can you update that? Also, can you share a screenshot of who currently has Create Issues permission in the Permission Scheme?