community.atlassian.com Open in urlscan Pro
2600:9000:214f:d600:12:54e9:5100:93a1  Public Scan

Form analysis
1 forms found in the DOM

Name: form_1077165a5a2556e — POST https://community.atlassian.com/t5/blogs/v2/blogarticlepage.searchformv3.form.form

<form enctype="multipart/form-data" class="lia-form lia-form-inline SearchForm" action="https://community.atlassian.com/t5/blogs/v2/blogarticlepage.searchformv3.form.form" method="post" id="form_1077165a5a2556e" name="form_1077165a5a2556e">
  <div class="t-invisible"><input
      value="blog-id/jira-articles/article-id/5964/q-p/dXRtX3NvdXJjZTpuZXdzbGV0dGVyLWVtYWlsOjp1dG1fbWVkaXVtOmVtYWlsOjp1dG1fY2FtcGFpZ246amlyYS1pbnNpZGVycy1uZXdzbGV0dGVyX2phbnVhcnktMjAyMl9FTUwtMTE3NjI6OmpvYmlkOjEwNTM5OTgwOTo6c3ViaWQ6MTUzMjYyMTYzOA.."
      name="t:ac" type="hidden"><input value="search/contributions/page" name="t:cp" type="hidden"><input
      value="xK6thM2biIR9HvjNTLxXXZL1d6xEmYF6stwSDL2rzsJzD9hHuIVsQ0ZHmO_pwKyOQTc-rotVy3-b8OVF5sEbN6hriGVQq2Hs2GkttTvh8wWKHzk3qXvTZz4OgxuWe3mQ_8uCes7vRmz1MZTtIGfxbpY09ntnWXpCIhBO_lMCXQXY64snCi2fO4lm2Soc3eUofc24kj58BMSQCO4_UJv8l9SfEvfNF68T0afRlto4yLOzQsZPyX2OV7HpF4WNuaVsBuNab6_lPVoGQcWQuzh_Q7tFWwzn_y8MRg-OuVpwwZwD3Zw46_39eVzj6WMMb6qJ2PJmpKckuVoTG7Jcg-l_WUtT5iZvgSur-389klhjzxs1HYFF4CMVFiu8NF_jfwbzUTL6xJTEOWpWobPifVsGG1bmG3_dlyQr70lesq5QBO46AR1o-dXWifwV_zkFi6A-SBDREouglXgmiX6pQeiekCRBxLrGeI87u0UKMr6dTq5b7FPdSMwOlYQtkSZIHqRZ92axVvAWALlkIQzLbsyB0ZHck_l-4rCKjuWNONrD5EizMKMvAYh08XPpvx0O_pAGAje8Q3FSsleCU7p6mNwpAsMdp8fnOQGFrRGhbeqokduL7V1ex_XEn8A4eZiI6_LfkX9NG46TPYeYaIs6h_c4ow7K0fMwDfhpKhFJOK_zmiW7lKBmtOQUQf1GZA9CruSqCk3B5JdhblbVhOXgVFm2nu97Coqv3iFTjpfKAWCqx1GgSgxdL_WB8fOYv9_mUNeYv6cKGIQgIpg0JFG9kd9dh9o_TWvEbLw64mHOIe1ByObr5Bc9P_lIfpZGOXUg_S2JuC88XHMKWNuAVTOE-2zdi25Or8QrVYr-Ds8zyzii2r7AdpyHnFADplZdFV3aaqCoUz3eOvcMh5Bl2sjtJTjDDNHU0nQs1c-lAOE4vWxciSLu-FVkp5DtcY6nfihKLlcfRJ_Zyq6A9nUGwPR66vW8o0ecYsKVvAQ8VlzZdy3E7mshvgbfD_lIov6e0KbStZX6od4nRY84-CAZa5Q6k3rBB7HOkyECpvliYiWnCv9o0SQ9KzemevxSrZwWUFcy491eX74fU0zGJyO2rN4IQb5mbUYM_L4qyktC3CSclrgvMRkjyT9Mew_UJUbP_aH6pKJqcquuwswB7wsfjb4jz1pPIcMEa_wsDwxxk_ewBukVtbt9oG8ROa273fR9cwC6U1hlFxSmqndJzbysSUNABTE97K5VgH3cRJKGoJkiACHpoYmp4SVFHvRk_Uc8g1kA8z0SeykDWhSq5-9wwfzn5C8BCtSheU5dNOmdYCcIoTLwm3k."
      name="lia-form-context" type="hidden"><input value="BlogArticlePage:blog-id/jira-articles/article-id/5964:searchformv3.form:" name="liaFormContentKey" type="hidden"><input
      value="9zKJRb2t6eBUSdsJE51rxcarwSY=:H4sIAAAAAAAAALWQMU7DMBSGH5U6VQgJwQ1gdZCgCxVDhVQxRKUoYka2+5oGkjjYTlMWjsIJEJfo0I07cABWJgbsJKBSkEigTJH/F/3f9979MzSzI+gopJKPHS5iLQOW6kDEyhlQHw+LyUjIaLJPVMqiQJcf+zNOtZLQFtInNKF8jETTBJWWN23ChcQwYIRRhaTLTEi57gUYDnc81Gmyez5rPW3PXxuw5kIrR4uwTyPUsOle0gl1Qhr7jmeMYr8zTTSsF+DjAvx3725d74EUHJXybI9SBjZ7GB6MXu4eGwDTJOuDW1EoMi0mLDPb/U2kruEWwFyjHHn5KDdZNcqSmtkZnFYs1Ves1gpbX1e42PsHXrHHCfQq9qYK5WLj0vtdf8Pmi+dfGaGucCz0pxMsvT+Ebf474R8IufAbDQePfjcEAAA="
      name="t:formdata" type="hidden"></div>
  <div class="lia-inline-ajax-feedback">
    <div class="AjaxFeedback" id="feedback_1077165a5a2556e"></div>
  </div> <input value="T1Vj0dzTOC_8XzaZX6ABaTA6T_OZR9fjtO86Fme-1vg." name="lia-action-token" type="hidden"> <input value="form_1077165a5a2556e" id="form_UIDform_1077165a5a2556e" name="form_UID" type="hidden"> <input value=""
    id="form_instance_keyform_1077165a5a2556e" name="form_instance_key" type="hidden"> <span class="lia-search-input-wrapper"> <span class="lia-search-input-field"> <span
        class="lia-button-wrapper lia-button-wrapper-secondary lia-button-wrapper-searchForm-action" title="Search***" aria-label="Search***"><input value="searchForm" name="submitContextX" type="hidden"><input
          class="lia-button lia-button-secondary lia-button-searchForm-action" value="" id="submitContext_1077165a5a2556e" name="submitContext" type="submit"></span> <input placeholder="Search" aria-label="Search" title="Search"
        class="lia-form-type-text lia-autocomplete-input search-input lia-search-input-message" value="" id="messageSearchField_1077165a5a2556e_0" name="messageSearchField" type="text" aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Awaiting your command</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="z0xUFd2IGgtyLYkShzZmYLbE1kVXa84rk3MrdjsDdCE." rel="nofollow" id="disableAutoComplete_1077165a5cfaa68" href="https://community.atlassian.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/jira-articles/article-id/5964/q-p/dXRtX3NvdXJjZTpuZXdzbGV0dGVyLWVtYWlsOjp1dG1fbWVkaXVtOmVtYWlsOjp1dG1fY2FtcGFpZ246amlyYS1pbnNpZGVycy1uZXdzbGV0dGVyX2phbnVhcnktMjAyMl9FTUwtMTE3NjI6OmpvYmlkOjEwNTM5OTgwOTo6c3ViaWQ6MTUzMjYyMTYzOA..&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div> <input placeholder="Search" aria-label="Search" title="Search" class="lia-form-type-text lia-autocomplete-input search-input lia-search-input-tkb-article lia-js-hidden" value="" id="messageSearchField_1077165a5a2556e_1"
        name="messageSearchField_0" type="text" aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Awaiting your command</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="Ho4b9nuYJUDpKMbb2EsAZvhBmKmE3lWIAcAbi4p8Jk0." rel="nofollow" id="disableAutoComplete_1077165a69c2f63" href="https://community.atlassian.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/jira-articles/article-id/5964/q-p/dXRtX3NvdXJjZTpuZXdzbGV0dGVyLWVtYWlsOjp1dG1fbWVkaXVtOmVtYWlsOjp1dG1fY2FtcGFpZ246amlyYS1pbnNpZGVycy1uZXdzbGV0dGVyX2phbnVhcnktMjAyMl9FTUwtMTE3NjI6OmpvYmlkOjEwNTM5OTgwOTo6c3ViaWQ6MTUzMjYyMTYzOA..&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div> <input placeholder="Search all content" ng-non-bindable="" title="Enter a user name or rank" class="lia-form-type-text UserSearchField lia-search-input-user search-input lia-js-hidden lia-autocomplete-input"
        aria-label="Enter a user name or rank" value="" id="userSearchField_1077165a5a2556e" name="userSearchField" type="text" aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Enter a user name or rank</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="mVYNnixkFsISvWhtJd9F4IRO1VxbIuorh7nG-TUi-Lw." rel="nofollow" id="disableAutoComplete_1077165a6d419b7" href="https://community.atlassian.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/jira-articles/article-id/5964/q-p/dXRtX3NvdXJjZTpuZXdzbGV0dGVyLWVtYWlsOjp1dG1fbWVkaXVtOmVtYWlsOjp1dG1fY2FtcGFpZ246amlyYS1pbnNpZGVycy1uZXdzbGV0dGVyX2phbnVhcnktMjAyMl9FTUwtMTE3NjI6OmpvYmlkOjEwNTM5OTgwOTo6c3ViaWQ6MTUzMjYyMTYzOA..&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div> <input title="Awaiting your command" class="lia-form-type-text NoteSearchField lia-search-input-note search-input lia-js-hidden lia-autocomplete-input" aria-label="Awaiting your command" value="" id="noteSearchField_1077165a5a2556e_0"
        name="noteSearchField" type="text" aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Awaiting your command</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="Bli7aakSQs8bReOzU5FXc0ceKCTzougH0X4QyY5Pb_I." rel="nofollow" id="disableAutoComplete_1077165a7069ff1" href="https://community.atlassian.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/jira-articles/article-id/5964/q-p/dXRtX3NvdXJjZTpuZXdzbGV0dGVyLWVtYWlsOjp1dG1fbWVkaXVtOmVtYWlsOjp1dG1fY2FtcGFpZ246amlyYS1pbnNpZGVycy1uZXdzbGV0dGVyX2phbnVhcnktMjAyMl9FTUwtMTE3NjI6OmpvYmlkOjEwNTM5OTgwOTo6c3ViaWQ6MTUzMjYyMTYzOA..&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div> <input class="lia-as-search-action-id" name="as-search-action-id" type="hidden">
    </span> </span> <span id="clearSearchButton_1077165a5a2556e" role="button" tabindex="0" title="Clear" class="lia-clear-field lia-js-hidden" aria-label="Clear the search input"></span> <span class="lia-cancel-search">cancel</span>
</form>

Text Content

Atlassian Community logo Products Interests Groups
Create
Ask the community 

 * ASK A QUESTION
   
   Get answers to your question from experts in the community

 * START A DISCUSSION
   
   Share a use case, discuss your favorite features, or get input from the
   community

Awaiting your command

Turn off suggestions
Awaiting your command

Turn off suggestions
Enter a user name or rank

Turn off suggestions
Awaiting your command

Turn off suggestions
cancel
Turn on suggestions
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

PRODUCTS

 * Jira
   Jira
 * Jira Service Desk
   Jira Service Management
 * jira-align
   Jira Align
 * Confluence
   Confluence
 * Trello
   Trello
 * 
   Jira Work Management
 * Sourcetree
   Sourcetree
 * Bitbucket
   Bitbucket
 * Opsgenie
   Opsgenie

See all

COMMUNITY RESOURCES

 * Feedback & Announcements
 * FAQ
 * Guidelines

SUPPORT

 * Technical support
 * Documentation
 * Atlassian Community Events
 * Atlassian University

INTERESTS

 * Feedback Forum
   Feedback & Announcements
 * Atlassian Cloud Migrations
   Atlassian Cloud Migration
 * Agile
   Agile
 * Atlassian logo
   DevOps
 * Off-topic
   Off-topic
 * Training and Certification icon
   Training & Certification
 * Atlassian logo
   Atlassian Account
 * AUG
   Atlassian Community Events

See all

COMMUNITY RESOURCES

 * Feedback & Announcements
 * FAQ
 * Guidelines

SUPPORT

 * Technical support
 * Documentation
 * Atlassian Community Events
 * Atlassian University

TOP GROUPS

 * groups-icon
   Welcome Center
 * groups-icon
   Atlassian Answerers
 * groups-icon
   Enterprise
 * groups-icon
   Trust & Security
 * groups-icon
   Community Events
 * groups-icon
   Industry Groups
 * groups-icon
   Learn from Home Study Groups
 * groups-icon
   Featured Groups

Explore all groups

COMMUNITY RESOURCES

 * Feedback & Announcements
 * FAQ
 * Guidelines

SUPPORT

 * Technical support
 * Documentation
 * Atlassian Community Events
 * Atlassian University


It's not the same without you

Join the community to find out what other Atlassian users are discussing,
debating and creating.

Sign up for free Log in

×
 * Community
 * Products
 * Jira
 * Articles
 * #JiraHeroes January '22 Spotlight: Soumen Deb


#JIRAHEROES JANUARY '22 SPOTLIGHT: SOUMEN DEB

Jan 10, 2022

At Atlassian, we take great pride in the software we ship, and even greater
pride in the success our customers achieve when they use our products.
#JiraHeroes is our new monthly spotlight series where we ask customers to share
their success stories with Jira Software. We hope that customers will find
inspiration on how to overcome their own challenges by hearing how our
#JiraHeroes overcame theirs.

This month, we’re featuring @Soumen Deb, a Quality Engineering and Assurance
Specialist at Cognizant Technology Solutions, who helped a client redesign a bug
workflow in Jira Software to improve reporting capabilities, increase
visibility, and streamline the development pipeline.

 


PLEASE INTRODUCE YOURSELF! TELL US ABOUT WHERE YOU WORK, YOUR ROLE, AND THE TEAM
YOU’RE ON.


Hello Community! My name is Soumen Deb, and I’m a Quality Engineering and
Assurance Specialist at Cognizant Technology Solutions, a leading multinational
insurance and financial service provider. My team and I are based out of
Singapore, and my team supports clients with Quality Engineering (QE) and
Quality Assurance (QA) practices for regional programs across the Asia-Pacific.



WHAT CHALLENGES WERE YOUR CLIENT FACING AND HOW DID THAT INFORM THE WAY YOU
THOUGHT ABOUT DESIGNING AN INTEGRATED BUG WORKFLOW?


I was working with an insurance and financial service provider that had several
agile teams, each with their own unique bug workflow in Jira Software. This
caused a variety of different problems such as: 

 * Monitoring, evaluating, and maintaining the health of the instance was
   difficult. Since bugs from different phases of tests had different workflows,
   transitions, and statuses, having an integrated view of the overall health of
   the program was almost impossible. The only workaround was to connect with
   each agile team individually, but this created a disjointed and siloed view
   of the overall system.

 * Creating reports and consolidating information was time-consuming. Since each
   team had their own bug workflow, reports had to be manually exported and
   consolidated outside of Jira Software. This left a large margin for human
   error.

 * Managing the volume of requests became more challenging. Irrespective of
   which team raised the bug request, they all needed to pass through the
   quality toll gates from lower environment to higher environment (quality
   assurance --> system integration testing (SIT) --> user acceptance testing
   (UAT) → pre-production). As the program got larger with more complex
   releases, tracking, fixing, and deploying bugs individually in the
   development pipeline became more challenging.

What we needed was an integrated bug workflow that was 1) compliant with
industry best QA practices and 2) had a clear, distinct view of bug statuses
across each phase of tests (InSprintQA, SIT & UAT). That is, every bug needed to
traverse the same flow so that statues and transitions are aligned across all
the stakeholders.

Since we already had Jira Software in our ecosystem, we knew adopting a
customized workflow would be an easy and robust solution. However, there were a
few things I needed to keep in mind during this process: 

 * This new bug workflow will be implemented with new projects only.
   Implementing a new workflow with inflight projects could have serious and
   negative impacts to existing data sets.

 * This new bug workflow will be reusable and easily adaptable across all the
   phases of tests (InSprintQA, SIT, UAT).

 * This new bug workflow will give program teams the ability to choose the
   critical path of the bug life cycle. That is, if a bug is raised in UAT, the
   bug needs to be fixed and deployed to QA env., followed by SIT env., and then
   to UAT env. to have integrity of the build across all the environments. This
   is the usual best practice followed. On the other hand, they will have the
   flexibility to deploy bug fixes directly into UAT in case InSprint & SIT env.
   are decommissioned.



HOW DID YOU DESIGN THE INTEGRATED BUG WORKFLOW IN JIRA TO MEET THE UNIQUE NEEDS
OF YOUR CLIENT’S ORGANIZATION?

 

UNIFIED VISION OF DOWNSTREAM WORK

Before creating a new bug workflow, I met with leaders of the agile teams to
learn more and understand the rationale behind the existing workflows. These
conversations were very informative, but one learning was the most insightful:
each team had the same goal of fixing and deploying bugs for retesting in the
next phase, but there was no vision beyond their respective scrum teams. The
teams needed an understanding of how their work flows downstream in order for
the entire organization to run smoothly. I kept this learning top of mind as I
designed the new bug workflow. 

AGILE ITERATION OF OUR WORKFLOW

Once this initial analysis was done, I drafted a new workflow in the sandbox
version of Jira Software. This was where I made regular changes to the workflow
based on the feedback I received from the scrum masters of each agile team. I
held recurring, weekly meetings with all scrum masters so that we could
establish a common vision and increase transparency of the redesign process. 

PILOT AND IMPLEMENTATION

Once we were settled on a new workflow, I created a dummy project and associated
this with the bug issue type. Then, I handed the workflow over to the quality
assurance team who ran several tests over the next 2 days to check all necessary
use cases. Once certified “OK”, our tools admin team rolled out the workflow to
a couple of projects during a “Pilot Phase”, where all aspects of this workflow
were highly leveraged. After making a few changes to the workflow based on
feedback from the Pilot Phase, the new workflow was ready to be rolled out to
new agile projects across all teams. 

The implementation of the new bug workflow was a huge success. Having a
streamlined bug workflow enabled our client to create better reports using Jira
Dashboards. The client’s management and executive teams were able to assess the
program’s health by looking at the number of bugs (By Severity, By Priority) in
each phase of tests under a single view. The client could also generate heat
maps for each test phase on defect prone Components and its RCAs. 

 


THINKING BACK, WHAT ARE SOME BEST PRACTICES YOU SHARE TO HELP OTHERS AS THEY
THINK THROUGH CREATING THEIR OWN BUG WORKFLOWS?

 1. The bug workflow should be easily adaptable by all agile teams. The state
    transitions and statues need to be understood by all the teams (e.g.
    Development, Business Analyst, Quality Assurance, Program Management,
    Executives).

 2. The workflow should cover all critical QA paths. The workflow should ensure
    that the bug passes through all quality toll gates and can then be pushed
    into the next phase.

 3. Introduce mandatory input fields so that the workflow is tightly aligned
    with QA processes. This is done so defect dumps can be used in analytics and
    retros. 

 


IN GENERAL, WHAT IS ONE PRO-TIP YOU COULD GIVE TO SOMEONE WHO’S A NEW JIRA
ADMIN?

Always try new workflows in the sandbox version. Do proper tests of all use
cases (which should be done by independent testers, not the one who are involved
in creating the workflow) before rolling out for pilot usage. Always keep a roll
back plan ready in case you need to revert back.

 

--------------------------------------------------------------------------------

 

Thank you so much for sharing your insights, Soumen! 🎊 Please feel free to
connect with Soumen on LinkedIn!

#JiraHeroes have extensive knowledge of Jira, and share their thoughtful and
tactical content with the Community! Are you inspired by Soumen’s story, or have
a story of your own to share? Check out our call for submissions, and let us
know you’re interested in the comments below to be featured and also receive our
coveted Jira Hero Community badge! 🙌🏻

Comment
Watch
Like 24 people like this # people like this
Share
 * LinkedIn
 * Twitter
 * Email
 * Copy Link

3763 views



1 COMMENT

Soumen Deb Community Leader Jan 10, 2022

A very nice start of 2022! I'm glad being part of #JiraHeros program. Thanks
@Rachel Tang for giving me an opportunity to share this experience! Cheers! 



Like • 6 people like this 6 people like this


COMMENT

Log in or Sign up to comment


WAS THIS HELPFUL?

Yes No

THANKS!

×

Rachel Tang

Atlassian Team

ABOUT THIS AUTHOR

Product Marketing Manager

6 total posts

 * 
 * 
 * 
 * 
 * 
 * 
 * +7 more...

View profile
Jira
Jira

TAGS

 * bug
 * cloud
 * customer
 * customer-spotlight
 * jira-cloud
 * jira-software
 * jira-software-cloud

Related Community content


 * #JIRAHEROES DECEMBER '21 SPOTLIGHT: JOSE LUIS GAIT...


 * #JIRAHEROES NOVEMBER '21 SPOTLIGHT: ALEXANDER BOND...


 * 🔈 CALLING ALL JIRA SOFTWARE EXPERTS: ANNOUNCING #...


 * YOU'VE GOT IT! JANUARY 22 IT IS!


 * JQL FOR ISSUES CREATED BETWEEN 22:00 & 00:00 FROM ...




COMMUNITY SHOWCASE

 * Understanding Issue Types in Jira
 * What are Issues in Jira
 * What’s the difference between a kanban board and a Scrum board?
 * New Portfolio Cloud Experience Beta
 * Announcement: Project Level Email Notifications for next-gen projects on
   JSW/JSD


DO YOU HAVE QUESTIONS ABOUT CLOUD MIGRATIONS?

You're in luck! We're hosting an AMA with Chris Clarke: Head of Product,
Migration Journey. Ask him any questions or provide feedback directly to the
whole migration team! Coming up January 31st.

Submit your questions


COMMUNITY EVENTS



Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Find events near me

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event.
Learn more about Community Events

EVENTS NEAR YOU


 * FAQ
 * Community guidelines
 * Privacy policy
 * Terms of use
   
 * © 2022 Atlassian




Auto-suggest helps you quickly narrow down your search results by suggesting
possible matches as you type.