nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

🎙️ Share your Plug into Jira story to unlock our new DevOps Story badges!

Annie Lu_480t6d

DevOps storyteller figma.png

Hi Atlassian Community! 👋

We’ve loved seeing your engagement with Plug into Jira, our recent series on how to up-level your Jira Software experience with integrations. Now, we want to hear from YOU: how does your team plug into Jira?

If your team uses Jira Software integrations for your software development workflows (SCM, CI/CD, security testing, feature flags, etc.), we'd love to learn more about your experience and any best practices or insights you can pass on to the Community.

To unlock our limited-edition DevOps Story Teller badge, share how your team* is using Jira Software integrations for your DevOps workflows.

Some sample integrations include: SCM (GitHub, GitLab, BitBucket, etc.), CI/CD (Bitbucket Pipelines, CircleCI, Octopus Deploy, GitHub, GitLab, etc.), Security (Snyk, Lacework, Mend, JFrog, Stackhawk, etc.), Feature Flags (LauchDarkly, Split, Harness, etc.), Project Pages (Confluence, Google Docs, etc.), Design & whiteboard tools (Figma, Miro, etc.)
Share your story as a discussion in the DevOps Community Group or as a comment on this post
Tag your post with #devops-story to make it easily discoverable to fellow Community members + our team
Make your DevOps Story as helpful to other Community members as possible by including:
- Some background on your team and the type of projects you're working on
- Which integration(s) you're leveraging in your DevOps workflows and how
- Challenges or pain points addressed by these integrations
- Any tips, tricks, learnings or best practices gained through your experience

*A special note for Partners: Have a customer whose DevOps story should be shared? Nominate them for storytelling opportunities through the new Partner Spotlight Program!

We launched two new DevOps Badges that you can earn when you share your DevOps story or comment on a discussion!

Earn 100 points and the limited DevOps Story Teller Badge when you complete all of the following:

Create a discussion with this link to answer the prompt and share your DevOps story
Alternatively, create a discussion manually and tag #devops-story
100 Bonus Kudos will be awarded to the best DevOps Story Teller post!

Earn 10 points and the DevOps Smooth Operator Badge when you comment on a #devops-story discussion (up to 5x per day)!

We hope this challenge is both fun and helpful for the DevOps Community. We can’t wait to hear your stories! Comment on this post and share your favorite DevOps tool or meme to jump-start this challenge!

Comments

Annie Lu_480t6d

This is a personal favorite that never gets old 😜

Ram Kumar Aravindakshan _Adaptavist_

Laurie Sciutti

🤣 Love the memes but I am interested to read what others have done to better facilitate DevOps processes.

Will Ryan

So far we have:

Change logs in Confluence that pull data from Releases in JIRA
GitHub integrations (e.g. AB-12345 #comment This goes into JIRA automatically)
GitHub Automations (e.g. Move ticket from To Do to In Progress when branch or PR created)
Assign tickets to Release Engineer when moved to Ready for Production column
Assign tickets to Lead Software Engineer when moved to Code Review column
Send message to Google Chat when a ticket is moved to Blocked column

Deepthi_bneguc

#devops-story

Hello Atlassian team, Glad to be a part here. All the products provided are sounds good to have. Challenges in learning and getting scores and badges are impressive DevOps are fab. A great experience in learning and working with this.

Mahesh Shinde_k4hefc

It's very good initiative to explore new way to provide the information and use the Atlassian tools to do better in Devops

Jira is important part in Devops cycle to track the progress in ticket as well as in Bitbucket Repo.
Bitbucket Pipeline is used in CI process to achieve the automation in development cycle.

#devops-story

Regards,

Mahesh Shinde

LynnG

Hi,

I am a fan of Jira and confluence. I am now working with a DevOps infrastructure team so I am motivated to learn how so support them best with Atlassian tools.

My teams love it when I enable the Development card label on the Active Sprint and Backlog view.

I am here to learn from those who have more experience.

Prasad Kalamkar

Got introduced to Devops during my New joining in the IT background of a BFSI Domain.

Dave Menconi_57aj5q

We built a framework that connected Jira to EVERYTHING. We had a workflow that would send a webhook to a server every time a ticket changed status. We used it like this:

A issue for a feature was create and added to a Epic.
When the issue transitioned to "ready for development" a development server was spun up and a Bitbucket branch was created in the appropriate place (based on the epic).
When the issue transitioned to "ready for test" a test server was spun up, the code from the branch was installed and the test suite was run on that server. When testing was complete it would automatically transition to "ready for review"
A human would review the results and either create bug tickets or pass it to "ready for integration". The branch would be merged with the main branch (with appropriate code reviewers notified).
When all the issues in the epic were in "ready for integration" a server would be spun up and the whole epic (a collection of related features) would be installed and all the tests run.
Then it would go to QA who would do whatever manual tests were still deemed necessary.
Then it would go to "ready for release" where one more transition would cause it to be release as the new version of our software in all our offices worldwide.

We originally had it planned so it would automatically release the software but we discovered that people didn't like having new features just appear: they wanted to have them explained to them first. So we made final release dependent on a human who had updated the documentation and verified that everyone had been informed.

Very nearly a complete automated release process, though.