Julien Béchade Specialist

Hi Trudy, It was indeed that global permission the user group was lacking. I feel a bit stupid to have overlooked the obvious but I did need to rubber duck it with someone. Thanks for your help ❤ Cheers. Julien.

Of course, silly me. We're using Atlassian Access to provision groups and users and that particular provisioning group was newly created hence not added to the Browse Users and Groups global permission. I fixed that now and will check with my colleague in the morning. I'll keep you posted. Thanks for your help! Cheers.…

Hi Trudy, Thanks for your help! Can you get a screen image from the user and a screen image of what you see and show us both? No, I cannot atm but those users only see their own user while I can see all of theirs. See picture below. Can you confirm that the user has not activated any Quick/Custom filters when they are…

Hi @Benjamin Paton Is there still a spot available to participate to the EAP? We've just set up Atlassian Access and would love to be able to enable SSO for internal and portal only customers. Cheers. Julien.

Hi @Ste Wright , The requirements for the weekly digest is email because the public is new to JIRA/JSM and is primarily using email so dashboard wouldn't be an optimal solution. But subscription looks like a good candidate before the CodeBarrel team implement a meaningful way to work further on the `lookupIssues` data. I…

Hi @Ste Wright and thanks for your help! I did not think about subscription at all and I'll explore that solution further, thanks! However, I need to be able to customize the email, order the different tasks per project and status, etc. and that does not seem to be possible with subscription. My Google research led me to…

Hi Patricia, Good to know. This behaviour is a bit unintuitive though but easy to fix. Thanks for your answer! Cheers. Julien.

Hi @Nic Brough -Adaptavist- and thanks for the answer. In my client's case it is not possible to click on those 3 dots. It is actually 3 big dots, exactly as follow [●●●●●]. So I really think it is maculated by Atlassian when sending the mail. When logging in to JSM, this user does have access to the content so it does not…

Hmm, no one encountered this issue yet then?

Hi Muhammad, @John Funk is right, Automation is your friend here. What we've done at our company is use the "Escalated" state to trigger a rule that will clone the JSM ticket to a JSW project of our choice then add a "Clones" link with the reference to the cloned JSM ticket. Furthermore, we've created several other rules…

My bad! I was getting an error every time I published a global rule and reading this , I assumed global and multi-projects rules where only from premium. You might want to update that support page. It turns out the account used as an actor was not an agent on the JSM project involved in the rule and that's why I was…

Thanks for your answer @Mark Segall The cost is definitively something we'll consider based on the number of agents or/and licensed users for JS. But what we seek to achieve requires global rules on multiple projects across both JS and JSM and that level of automation is off limit on the standard plan. That's why I was…