Atlassian Jira vs. Receptive.io (discontinued)

Jira facilitates software development, bug tracking, and sprints. It's ideal for structured workflows, issue management, and customer communication. However, more straightforward tools might be more efficient for highly creative, unstructured tasks or tiny, agile teams with quick visual overviews. Jira's complexity can be overkill for basic task lists.

Incentivized

Receptive is very effective for multiple internal teams/department of a single product who need to scale their product feedback management effectively. We've been leveraging it for one of our products and it was so successful, that we implemented it with a second product. The main issue we ran into situationally with that was managing 2+ modules (products) in Receptive; it was a bit more difficult to present Receptive to two different customer bases/users (we couldn't change the appearance) and slightly confusing to do within the app (lots of filtering needed). I have heard that support of multiple modules is something that Receptive will likely be working on in the near future, so that's good news.

Incentivized

• Integration of tools like Bitbucket, Github, etc., has made it easier to track the code changes, pull requests, and branches linked to the respective ticket.
• The detailed tracking system in JIRA has helped the teams prioritize and understand the project tasks and issues.
• JIRA's project tracking board helps you keep track of the project, its flow, and expectations in a structured format.

Incentivized

• Captures feature requests from customers
• Organize feature requests
• Communicate progress updates to customers

Incentivized

• The interface is not intuitive to learn for new users
• JQL is similarly challenging for newbies
• It's possible to accidentally move issues from one sprint to another without realizing your mistake
• Certain issue attributes aren't available in certain view (e.g. story points from the epic overview)

Incentivized

• Filtering in general is not easy
• I would like to be able to create a leadership priority dashboard
• I would like to know easily when something has been linked to Jira

Incentivized

This is because Jira Software generates a huge profit for an affordable price. Having a tool that makes team management transparent and effective is very valuable.

In addition, the renewal of Jira Software and all Atlassian tools is predictable and clear, as the prices are published on the Atlassian website and there is no pyramid of intermediaries.

Incentivized

The interface is simple and easy to use if you have some experience with it. Configuration is also logical most of the time. However, less experienced users tend to find themselves lost in some tasks - usually complex project configuration- but sometimes simple things, such as seeing why a user can't move issues in a workflow. Jira configuration requires a good amount of experience - and even experienced users often resort to documentation. It's a tool that's easy to use if you know what you're doing and where to find the proper documentation, but novice users tend to find it challenging.

Incentivized

Did not face any issues and whenever they plan maintanance they update all of us very well in advance also so in that view we are good with the product stability.

Incentivized

Performance is really good though it holds lot of data it loads quickly especially search operation also get the results very quickly as needed hence its good

Incentivized

I have not had a chance to contact JIRA's customer support. It does offer extensive documentation, although it often feels too technical for me. There is also a JIRA training app that lets you take little lessons and quizzes on different areas (e.g., JIRA basics, agile). I did find it a helpful way to teach myself.

Incentivized

I have not had a lot of contact with support, but when I do it's quick and accurate info.

Incentivized

Had received training from our own internal user so it was good and also very easy to understand topics and many tasks in the UI are self explanatory and we can do by our own

Incentivized

One of their strong points i stheir documentation. Almost all of the basic set up needed within JIRA is available online through atlassian and its easy to find and very precise. The more critical issues need to be addressed as well and hence the rating of 8 instead of a 9.

Incentivized

Take your time implementing Jira. Make sure you understand how you want to handle your projects and workflows. Investing more time in the implementation can pay off in a long run. It basically took us 5 days to define and implement correctly, but that meant smooth sailing later on.

Incentivized

monday.com cannot be integrated with CI/CD tools, whereas Atlassian Jira integrates with CI/CD tools seamlessly. Atlassian Jira has strong Agile and Scrum support. Coming to monday.com, it has basic agile functionality. But Atlassian Jira has a complex UI, and monday.com has an intuitive, drag-and-drop interface. Overall, Atlassian Jira provides features like Agile project management, DevOps integration, and customizable workflows.

Incentivized

We had UserVoice prior to Receptive but it was just too clunky and extensive for our needs. It was less about automation and still very manual work to process feedback. It also didn't provide collaboration levels that we needed for our internal teams to work together. ProdPad was a very clean tool but also didn't enable us to automate the process like Receptive does.

Incentivized

Product is rellay good but pricing part I am not aware

Incentivized

Atlassian Jira is highly stable and good with its performance and its has all the required scalability features as business needs

Incentivized

• Atlassian Jira's robust workflow automation has boosted team efficiency, shortening delivery cycles and driving a positive ROI through improved project management.
• Its advanced reporting and integration capabilities have enabled data-driven decisions, aligning operations with key business objectives.
• However, the steep learning curve can delay adoption, potentially hindering short-term ROI.

Incentivized

• We were managing these enhancements in our support ticketing system, using spreadsheets, and it was TERRIBLE. Being able to tell a user "Great idea! Submit it to Feedback!" has saved my support team hundreds of hours.
• We have reduced incoming support requests when the request is really an enhancement - the ability to have a "Suggest Features" widget in our software sends users straight to Feedback.
• Because we can make some fields required, we can cut down on the need to reach back out to our users for clarification.

Incentivized