John Funk Community Champion

Hi Santiago, My understanding is yes, it is coming. But I don't know the timeline for it. 

Hi Kevin - Welcome to the Atlassian Community! The issues must be in the last column on the Scrum board (far right) regardless of what Status they are in. 

you should probably contact the vendor then for support. 

Hi Kevin, You can run a query in the search for Watcher = account ID or name of user Then click the 3 dots menu and select Bulk change. Follow the prompts to choose all of the issues. Then Choose Stop Watching Issues. 

Hi Blake - Welcome to the the Atlassian Community! You can create a Timeline for a single project. But you will not be able to create Plan, which allows multiple projects in a single Plan without the Premium version. 

Well, that doesn't make a lot of sense me, but to each it's own. Regardless, it's all or nothing. You either get the email for everything you do, or nothing. 

Hi Kevin, Check the workflow and the post functions on the transition to Need Info

Hi Dilli - Welcome to the Atlassian Community! Run the Permission Helper while you are in the Permission Scheme.

Hi Luc - Welcome to the Atlassian Community! Why would you need that? You should be using Jira for all of your communication on the issue. 

Have you created anything at all? Can you share that? 

Sicher. Sie könnten einen kostenpflichtigen Plan mit nur ein paar Benutzern haben und dann kostenlose Gastkonten. Aber jeder Gast kann nur auf einen einzigen Space gleichzeitig zugreifen.

Hi Ronan, I had to go a very round about way to get there. Go to Settings > Billing Then click on Manage beside one of your products - probably Jira Then click the Invoices menu option on the left menu. This should show your previous invoices. 

Hi Gene - Welcome to the Atlassian Community! Yes, you should be able to do that. Give it a try and then post your rule back here if you need assistance. 

Nein, es ist im Rahmen des kostenlosen Plans nicht möglich, den Zugriff eines Benutzers einzuschränken.

Ah, tut mir leid, das liegt daran, dass Sie den kostenlosen Plan haben. Gäste sind darin nicht verfügbar. https://www.atlassian.com/software/confluence/pricing

Hi Chandrakumar - Welcome to the Atlassian Community! See this post I just did: https://community.atlassian.com/t5/Jira-Service-Management/Why-emailed-request-emails-are-suppressed/qaq-p/2767051

Hier ist der Leitfaden auf Englisch. Hoffentlich können Sie ihn übersetzen. https://support.atlassian.com/confluence-cloud/docs/invite-guests-for-external-collaboration/

There's no real information there. It is very vague about the actual cause/problem and the solution. It sounds like an Atlassian fairy will just show up and fix it. 

Hi Santhosh, My understanding is that invite emails especially get sent before the email account is fully setup on the customer end. When that happens, Atlassian gets a response back that this is not a valid account. So it goes onto the suppression list. It might appear to be whole domains sometimes because multiple…

That's not an acceptable answer.

Are you using a particular test app? 

Hola Ana: ¡Bienvenido a la comunidad Atlassian! ¿Estás usando una aplicación complementaria como Tempo? ¿O algo mas?

Can you share what you have so far? Are you using an automation rule to populate the Approvers field with the Reporter? 

Probably best to get Atlassian support involved at this point. https://support.atlassian.com/contact/#/

Okay, great. Please share your rule along with showing the details of the email text/body. 

Hmm, that's weird. Does it work later if you try it? Or just never for that issue? And you are manually updating the status? Is there any validator or condition or post function on the transition that might be interfering?

Yes, you should be able to do that. Maybe you create a custom field that is a radio button or yes/no dropdown or something like that. Then when you do a move from one project to another you mark that as yes. Maybe the name of the field is Triaged? or something like that. Then you can create a custom number field that you…

That's correct. You can't have it both ways. One of the sub-task issue types will always be the default. You can't change that by parent type. 

You are welcome.

You are welcome!