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

Welcome back, Jira enthusiasts! 🙌 

While Jira is widely recognized as a powerful tool, a world of practical features often goes unnoticed. Fear not, for we have Agata Grzelczak, Senior Quality Assurance Automation Specialist and Technical Leader at Deviniti, who has unearthed some remarkable insights for your benefit. Let's dive in and discover the untapped potential of Jira together! 🔍

Jira is more than meets the eye! From advanced permissions to customized actions, Jira provides a multitude of practical functions. Agata highlights the importance of familiarizing yourself with these features to leverage their benefits in your projects. By mastering the intricacies of Jira, you can optimize your workflow and enhance project management efficiency 💡

This valuable expertise will undoubtedly boost your overall efficiency in Jira. Stay tuned for more insights to enhance your ventures with Jira 📚

So, fellow Jira enthusiasts, let's embark on a journey of discovery. Uncover the hidden gems within Jira and unleash its full potential in your projects. With Agata's guidance and these valuable tips, you're well on your way to conquering Jira like a pro! 💪✨

image (2).png

image (3).pngimage (4).png

I hope you find these tidbits useful. More to come soon! 🤩

Also check out the first part of this series HERE.

Cheers,

Oliwia

9 comments

Yatish Madhav
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 22, 2023

Thanks again for this ...

Oliwia Poświat _Deviniti_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 22, 2023

@Yatish Madhav The pleasure is all ours :)

Michal Sefara
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 22, 2023

Hi, thanks for educating the public with your tips :) 

I have a question regarding the Resolution update:
what is the reason to choose a specific status instead of "any status" to "itself"?

And a minor thing: it seems that the 3rd point suggests using bulk change on a single issue

Tomislav Tobijas
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 22, 2023

Interesting stuff, so keep it up! 👀 I've read the first one, but would you mind linking part one somewhere in the article as well? I guess it could be useful to other members. Or maybe just add a tag/label to it?

Oliwia Poświat _Deviniti_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 22, 2023

@Tomislav Tobijas Thank you for your accurate observation! I added the tag: jira-curios and linked to part one :) Have a nice day!

Like Tomislav Tobijas likes this
Oliwia Poświat _Deviniti_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 22, 2023

Hi @Michal Sefara 🙌 

If you do not want to change the status and additionally do not want it to be possible to go to this status from other statuses, then a better solution would be to do it using the "itself" transition.


Example: The task is closed, but the wrong resolution has been set. You don’t want to make it possible to change the status from "to do" to "close". By using the "itself" transition, you can change the resolution without changing the status. But of course, you can use this method on any other transition. According to the "minor thing" question, yes, you can do bulk editing on a single issue or on any other number of issues for which you want to change the resolution.

I hope I fully answered your question!

Cheers,

Oliwia

Justyna Gdowik _ Deviniti _
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 22, 2023

Great content💡

Michal Sefara
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 22, 2023

Hi @Oliwia Poświat _Deviniti_ ,

that is exactly my point. If I don't want to change the status during the transition (as in the original case and your example) and can serve multiple statuses with a single transition (e.g. there might be several end statuses and issues that need to/might need to be updated in the future), why would I rather link the transition with a specific status?

I'm aware of the functionality, my remark/question was rather about the efficiency of such action.
I assume it's only a typo in "issues"?

Cheers,
Mike

Oliwia Poświat _Deviniti_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 25, 2023

Hi @Michal Sefara 

It really depends on what you need. If you prefer to allow all statuses to transition to this one, you can do it. But if you don’t want to allow users to change to other statuses, then it’s better to use the “to itself” transition. When it comes to efficiency, in Agata's opinion, it doesn’t matter if you use “to itself” or “all”. It just depends on what access you want to give to perform transitions by users.

Cheers,

Oliwia

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events