Jira

Jira

Business Tools / Collaboration / Issue Tracking

Decision at Atlassian about Azure Pipelines, jFrog, Octopus Deploy, AWS CodePipeline, CircleCI, Bitbucket, Jira

Avatar of ojburn
Architect at Atlassian ·

We recently added new APIs to Jira to associate information about Builds and Deployments to Jira issues.

The new APIs were developed using a spec-first API approach for speed and sanity. The details of this approach are described in this blog post, and we relied on using Swagger and associated tools like Swagger UI.

A new service was created for managing the data. It provides a REST API for external use, and an internal API based on GraphQL. The service is built using Kotlin for increased developer productivity and happiness, and the Spring-Boot framework. PostgreSQL was chosen for the persistence layer, as we have non-trivial requirements that cannot be easily implemented on top of a key-value store.

The front-end has been built using React and querying the back-end service using an internal GraphQL API. We have plans of providing a public GraphQL API in the future.

New Jira Integrations: Bitbucket CircleCI AWS CodePipeline Octopus Deploy jFrog Azure Pipelines

12 upvotes·32.7K views

Decision about Jira, Trello

Avatar of havlajznik
Freelancer at havlicekpetr.cz ·
JiraJira
#Trello

I use Jira because

  • It's used widely as the best SW dev tool
  • It's so easy to use
  • Flexible to configure
  • Great for tracking of tickets while leading meetings
  • Accessible from Everywhere

In overall, especially for large projects, Confluence is must. On the other hands, for small-mid size projects, #Trello is also great due to visualisation power.

11 upvotes·4.3K views

Decision at Herman Miller about GitHub, Confluence, Jira

Avatar of davidritsema
Frontend Architect at Herman Miller ·

We knew how we wanted to build our Design System, now it was time to choose the tools to get us there. The essence of Scrum is a small team of people. The team is highly flexible and adaptive. Perfect, so we'll work in 2 week sprints where each sprint can be a mix of new R&D stories, a presentation of decisions made, and showcasing key development milestones.

We are also able to run content stories in parallel, focusing development efforts around key areas of the site that our authors need first. Our stories would exist in a Jira backlog, documentation would be hosted in Confluence , and GitHub would host our codebase. If developers identify technical improvements during the sprint, they can be added as GitHub issues and transferred to Jira if we decide to represent them as stories for the Backlog. For Sprint Retrospectives, @groupmap proved to be a great way to include our remote members of the dev team.

This worked well for our team and allowed us to be flexible in what we wanted to build and how we wanted to build it. As we further defined our Backlog and estimated each story, we could accurately measure the team's capacity (velocity) and confidently estimate a launch date.

10 upvotes·6.5K views

Decision at Katana MRP about Papertrail, appear.in, Bitbucket, Confluence, Intercom, Jira, Slack, Requirements, Documentation, Alerts, ContinuousDelivery, InProductCommunication, Release, Logging, SourceCode, Notes, CustomerSupportChat, Agile, RemoteTeam

Avatar of pk-katana
Engineering Lead at Katana MRP ·
PapertrailPapertrailappear.inappear.inBitbucketBitbucketConfluenceConfluenceIntercomIntercomJiraJiraSlackSlack
#Requirements
#Documentation
#Alerts
#ContinuousDelivery
#InProductCommunication
#Release
#Logging
#SourceCode
#Notes
#CustomerSupportChat
#Agile
#RemoteTeam

As a new company we could early adopt and bet on #RemoteTeam setup without cultural baggage derailing us. Our building blocks for developing remote working culture are:

  • Hiring people who are self sufficient, self-disciplined and excel at video and written communication to work remotely
  • Set up periodic ceremonies ( #DailyStandup, #Grooming, Release calls and chats etc) to keep the company rhythm / heartbeat going across remote cells
  • Regularly train your leaders to take into account remote working aspects of organizing f2f calls, events, meetups, parties etc. when communicating and organizing workflows
  • And last, but not least - select the right tools to support effective communication and collaboration:
  1. All feeds and conversations come together in Slack
  2. #Agile workflows in Jira
  3. InProductCommunication and #CustomerSupportChat in Intercom
  4. #Notes, #Documentation and #Requirements in Confluence
  5. #SourceCode and ContinuousDelivery in Bitbucket
  6. Persistent video streams between locations, demos, meetings run on appear.in
  7. #Logging and Alerts in Papertrail
8 upvotes·1 comment·7.1K views

Decision at Katana MRP about Sketch, InVision, Slack, Microsoft Office 365, Jira, GitHub, Bitbucket, Confluence

Avatar of pk-katana
Engineering Lead at Katana MRP ·

How we ended up choosing Confluence as our internal web / wiki / documentation platform at Katana.

It happened because we chose Bitbucket over GitHub . We had Katana's first hackaton to assemble and test product engineering platform. It turned out that at that time you could have Bitbucket's private repositories and a team of five people for free - Done!

This decision led us to using Bitbucket pipelines for CI, Jira for Kanban, and finally, Confluence. We also use Microsoft Office 365 and started with using OneNote, but SharePoint is still a nightmare product to use to collaborate, so OneNote had to go.

Now, when thinking of the key value of Confluence to Katana then it is Product Requirements Management. We use Page Properties macros, integrations (with Slack , InVision, Sketch etc.) to manage Product Roadmap, flash out Epic and User Stories.

We ended up with using Confluence because it is the best fit for our current engineering ecosystem.

7 upvotes·30.2K views

Decision at StackShare about Markdown, GitHub, Trello, Jira, Agile, StoryPoints, TrelloPowerUps, StackDecisionsLaunch, Startup, Kanban, Massive

Avatar of johnnyxbell
Sr. Software Engineer at StackShare ·
MarkdownMarkdownGitHubGitHubTrelloTrelloJiraJira
#Agile
#StoryPoints
#TrelloPowerUps
#StackDecisionsLaunch
#Startup
#Kanban
#Massive

So I am a huge fan of JIRA like #massive I used it for many many years, and really loved it, used it personally and at work. I would suggest every new workplace that I worked at to switch to JIRA instead of what I was using.

When I started at #StackShare we were using a Trello #Kanban board and I was so shocked at how easy the workflow was to follow, create new tasks and get tasks QA'd and deployed. What was so great about this was it didn't come with all the complexity of JIRA. Like setting up a project, user rules etc. You are able to hit the ground running with Trello and get tasks started right away without being overwhelmed with the complexity of options in JIRA

With a few TrelloPowerUps we were easily able to add GitHub integration and storyPoints to our cards and thats all we needed to get a really nice agile workflow going.

I'm not saying that JIRA is not useful, I can see larger companies being able to use the JIRA features and have the time to go through all the complex setup to get a really good workflow going. But for smaller #Startups that want to hit the ground running Trello for me is the way to go.

In saying that what I would love Trello to implement is to allow me to create custom fields. Right now we just have a Description field. So I am adding User Stories & How To Test in the Markdown of the Description if I could have these as custom fields then my #Agile workflow would be complete.

#StackDecisionsLaunch

7 upvotes·20.9K views

Decision about Slack, OpsGenie, GitHub, Jira, Mattermost

Avatar of Aghmat-Abrahams-IR
Junior Data Engineer at Impact Radius ·

Slack is the industry standard for managed instant messaging (IM). A good alternative would be to self (or cloud) host an open source IM such as Mattermost but as always it would be a good idea to do a cost benefit analysis between the solutions.

Some of the main things to consider:

  • Having a good SDK for plugin creation
  • Having good integrations with existing tools ( JIRA , GitHub , OpsGenie , etc.)
  • Cost
  • Maintenance and administration
  • Covers all your businesses use cases
5 upvotes·10.5K views

Decision about Bamboo, Confluence, Jira, Redmine

Avatar of chrisfnz

We were using a hosted version of Redmine to track defects and user stories originally. We migrated to Jira.

Jira was an easy decision for a number of reasons:

  • It's much more "Scrum ready" straight out of the box
  • It's so much easier to keep a track of progress (I love the reporting)
  • It natively encourages you to adhere to Scrum/Agile/Kanban practices
  • Atlassian has a fantastic DevOps ecosystem when considering the likes of Confluence and Bamboo etc
  • So many integrations!
  • Its UI is so intuitive which makes it an absolute pleasure to use!

I know there are alot of other tools in this space but not even considering anything else at the moment. Love Jira!

5 upvotes·5K views

Decision at Storm8 about Jira, Pivotal Tracker, ProjectManagement, AgileProjectManagement, IssueTracking, Collaboration

Avatar of nasserkhan
Product Manager at StackShare ·
JiraJiraPivotal TrackerPivotal Tracker
#ProjectManagement
#AgileProjectManagement
#IssueTracking
#Collaboration

Over time, as our teams became bigger and projects became more complex, we started to take agile processes more seriously and wanted more advanced (by our standards) project management abilities, like burndown charts, velocity tracking, etc. We also wanted to handle a lot of content management tasks that were primarily done by non-technical teams but often touched engineering.

After using Pivotal Tracker and Wrike, JIRA ended up being the right choice for us. Its design was flexible enough to do engineering project management, content management and other tasks like product roadmapping effectively. It had all the bells and whistles we wanted (plus many more we never got around to using). Given that it is a flexible service that tries to do everything, it is ideal for a team that can 1) dedicate significant bandwidth to upfront setup and organization and 2) empower admins to establish and enforce best practices among team members.

#Collaboration #IssueTracking #AgileProjectManagement #ProjectManagement

4 upvotes·3.9K views

Decision at SeatGeek about Jira

Avatar of PavelRephiah
SRO Engineering Director at SeatGeek ·

Jira

We are using JIRA cloud and in general we happy with this tool for the following reasons:

  1. It is relative fast

  2. Confluence comes from same Atlassian company

  3. Easy to use and learn

  4. Easy configurable

  5. A lot of existing integrations with other tools

  6. Large marketplace with a lot of plugins.

4 upvotes·989 views