John Funk Community Champion

Made mine, too! Thanks for testing that out. Will be the best two beers I have bought in my life ;-)

@Simmo - Holy Cow! If that works, I now owe you TWO beers whenever I meet you!!

Hi @[deleted] - Welcome to the Atlassian Community! You can do this a couple of ways. 1. Set the value of the Reviewer field = to the value of the Reporter field using a post function on the transition to the Review status. Use the Copy Value From Other Field option for the Post Function. 2. Create a rule using Automation…

Hi Shivi, A status transition and saying once a field moves into a particular status is the same thing. You should put a Validator on the transition to the Pending status to make the field required. 

Great! Glad it is working for you now!

Hi @Iro Karavasili I hope I am following you - but you are not going to be able to control who the administrators for Project B wish to grant access to their project. If they choose the external group, you can't prevent that. It is more education that anything. You might could label the external group with a name that is…

Hi Vish - Welcome to the Atlassian Community! You can do that by having an Automation For Jira rule update the field on create.

Please come back here and update the thread once you get it all worked out. Thanks!

Sounds like something weird is definitely going on. I would go ahead and open a support ticket with Atlassian. https://support.atlassian.com/contact/#/

It will be easiest to see the examples. :-)

Hi Loretta, I would have your IT folks intercept the email to his company email if they are not already. Then have the system send him a Password Reset. Get that from the email, reset his password in Jira. Then log in as him and remove him from the admin groups. After that, you can log in as an admin and deactivate him. 

Hi Jonathan, It is very easy for filters to get changed with realizing it. I would just update the filter to be sure it is using the right columns you want. 

Está diretamente sobre a questão. Não tenho certeza do que é chamado em português. Em inglês, é "Watcher".

Also, take a look at this. It's a brand new feature rolling out from Automation For Jira. Might be the bulk email thing you want. :-)…

I would start with why so many emails are getting sent. Why does every person on a ticket need to get notified when every single thing happens? That's eating up your emails, but your users HAVE to hate that. Why not create a dashboard for each user and setup an activity stream on each dashboard. That way they can go look…

Se o usuário for um Observador do problema, ele será notificado. Caso contrário, você precisará enviar um email.

Can you share a screenshot of what you had?

Hi Natalie - Welcome to the Atlassian Community! Issues/Cards appear on board based on the filter attached to the board. Cards are not really created in Boards, they are just created against a project. Then the filters for the boards determine where the cards show up. So, take a look at the filters for the boards to see…

Great! Glad I could help a little. :-)

Hi Ugur, Are the Child Issues (1,2, 3) always the same when you create a story? In other words, when I create a new story, I always want these same 3 Children created. OR you just want to copy the Children from Story 1 every time? If so, I am assuming that you are linking Story 2 to Story 1 so it would know what Children…

Peço desculpas, mas você precisará do aplicativo de mercado JMWE para enviar o email da função de postagem. Aqui está mais informações sobre como fazer uma regra de Automação para Jira: * Vá para Configurações do projeto> Automação do projeto (no menu à esquerda) * Pressione Criar regra no canto superior direito *…

Si, es lo mismo. 

That did not yield the same results for me. It include issues that just moved to Open yesterday. 

Hi Chris, Here is a link to the roadmap for Next-gen projects. You can get a little more insight into what is coming for Done issues on Next-gen boards. https://www.atlassian.com/software/jira/whats-new/next-gen?_ga=2.104316484.513035551.1586779195-1313086432.1576012938#intheworks

Hola Jerónimo: ¡Bienvenido a la comunidad de Atlassian! Puede ocultar proyectos de un usuario cambiando el Esquema de permisos para el proyecto y modificar quién puede ver el permiso Examinar proyecto.

Hi Jonata - Welcome to the Atlassian Community! You can create an Automation For Jira rule that uses a Schedule component to run at a certain time. Then add the JQL you want to run it against (basically a filter). Then add a component to the rule for Edit Issue. Select the Labels field and just leave the This field will be…

No, just because someone is a "Jira Organisation Admin" does not give them access to all projects. They are still subject to whatever the permissions are for Browse Project in the Permission Scheme. I think the default is probably to add the Administrators group to the Project Role Administrators when a project is created.…

Hi Julien, Take a look at the Permission Scheme for the project. And while there, you can run the permission helper for that user to see why they are not allowed to see the issue. That will guide you to the solution for the user to be able to see the issue. 

What happens if they use too many commas? :-) I think your best bet would be to create some type of custom field(s) and then copy and paste values from the description field into those fields. Then you could setup an Automation For Jira rule to create issues when the field is updated (from being empty). Otherwise, not sure…

Thanks for the opportunity!!