Part Three: Jira Curios Unveiled! 🙌 Discover the secrets of Jira! 🔍

[#1]

Hello Community!

📣 We present to you the third part of interesting facts about Jira! You can find the previous two here and here.

Are you looking to enhance your Jira game and make your daily project ventures even more efficient? We've got you covered! Our very own Senior QA Automation Specialist and Technical Leader, Agata Grzelczak, has compiled a treasure trove of interesting and valuable facts that will turbocharge your Jira experience.

Think you've mastered all the features in Jira? Think again! Jira is a dynamic tool that constantly surprises and delights its users with new possibilities. Whether it's a hidden shortcut, a powerful function, or a fresh perspective on ticket management, there's always something new to discover.

These insights and tips will undoubtedly provide you with that "aha!" moment, helping you find that one feature or approach that revolutionizes your workflow. From time-saving shortcuts to innovative ticket management techniques, Agata's expertise will elevate your Jira experience to new heights.

So, whether you're a Jira veteran or just starting your journey, don't miss out on this golden opportunity. Let Agata take you on a journey of discovery and unlock the full potential of Jira.

Happy exploring! Let us know if you find these tidbits useful!

Oliwia from Deviniti

[Yatish Madhav]

Thanks once again for these ...

Note sure I understand the title of the first tip here. I think the points lead to creating an email channel, not creating a request in multiple projects?

Love the 2nd point. It boggled my mind just a few weeks back and figured it out. 

Thanks

[Oliwia Poświat _Deviniti_]

Hi @Yatish Madhav 

The first title leads to the creation of an email channel. If you send an email to those addresses, then requests will be created in multiple projects with one click. 

Thank you for your kind words, more curios coming soon! 🔥

Cheers,

Oliwia

[Yatish Madhav]

Hi - thanks for the response. Just want to clarify please :) 

"requests will be created in multiple projects with one click" - that tells me that more than 1 issue will be created in more than 1 project from just 1 email ... Is that true/possible? If so, how? :)

[Oliwia Poświat _Deviniti_]

@Yatish Madhav If you have two (or more) projects with configured email channels and send 1 email to those 2 (or more) addresses than more than 1 request is created. 

I hope we answered your question :)

[Andrew Laden]

For item 1, using a single email to create tickets in multiple projects. This is a really bad practice. For a few reasons.

This can lead to lots of confusion, as multiple people can end up working on the same issue, interfering with each other, and no single issue will capture all the work done on the issue. The issues aren't even linked to each other, so you would have no way of knowing that someone else is looking at the issue.

In addition, what happens with email threading in that case? if/when someone replies to the email, which issue gets the comment? Again can lead to comments not appearing when you think they would, and lost work, or conflicting changes.

I really wouldn't be "highlighting" a feature that sounds more like a bug to me. 1 email should create 1 issue, not multiple issues in different projects.

[Yatish Madhav]

Thanks for clarifying @Oliwia Poświat _Deviniti_  - I understand now - also I do agree with @Andrew Laden  though i think it is a real nifty trick that may have its benefits and use cases. Thanks again

[Oliwia Poświat _Deviniti_]

Hi @Andrew Laden 

Thank you for sharing the feedback and concerns regarding the practice of using a single email to create requests in multiple projects.

I understand your perspective and the potential issues it can lead to such as confusion or difficulties when it comes to email threading and managing comments and changes effectively. But like every curio, it is only an example, and as an admin, you should adjust it to your environment. As @Yatish Madhav mentioned it may have its benefits and use cases and we also think so.

Cheers,

Oliwia