You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We use the cloud-version of Jira in our company (as well as Confluence).
I have used Confluence before but I am new to Jira, coming from Azure DevOps and (and Microsoft Team Foundation before that). I have found it quite easy so far to find my way around, I just need to make sure I use everything correctly within our organisation for correct visibility and reporting.
I really like the links you create in the text of an issue directly into a section within a Confluence page, so no need to copy paste bits of explanatory text or create summaries of the same thing in two places.
I was a bit surprised that you can create issues (coming up as Tasks) directly within the Epic dialogue, without having to define Features and Stories in between. It's quite handy though, it looks like the issue-types are all quite similar anyway while sub-tasks allow sufficient subsequent breakdowns anyway.
Even though I liked having everything integrated in Azure DevOps (like source-control, builds and releases, for which we use separate products like BitBucket, Team City, ProGet and Octopus) it is refreshing to use something else than Microsoft - there are some handy features in Jira.
I will no doubt have some questions so it should good to be on here.