RALLY to JIRA Migration

Hi,

I am currently using RALLY for agile project management, test case management and defect tracking tool. But planning to use JIRA as unified project tracking system. I am sure that
defect tracking can be done in JIRA but please advise whether the below listed point can be covered in JIRA.

Ability to configure the Workflow of a defect (perhaps need to support multiple workflows?)
Ability to link/relate an issue to another
Track history of an issue (view everything from status changes to tracking who added notes/comments to the issue)
Ability to update defects in a batch
Reporting capabilities
Time Tracking?
Ability to add attachments
Ability to create views (able to see only the list of issues for one release)
Ability to email the issue to someone.
Notification (preferably email) when a defect is updated.
Permissions - restrict certain users from changing the status.
Ability to copy a bug
Ability to create custom fields – check for code review & test case review


Also JIRA will be better replacement for agile project management and test case management tools.

Show some lights on this.

Thanks,
Yuga

4 answers

2 votes

Jira does all of those (including multiple workflows).

Choosing between Rally and Jira is a hard choice, Rally is very good, especially for PMs, but Jira is a lot more flexible - if you're in a large organisation, you'll find Rally gets used for development project stuff, and works well (including some test management). You'll find Jira is used for the same, but then ends up being used to handle all sorts of other stuff - change control, risk management, helpdesk, devops, and even things like to-do lists and asset tracking.

0 votes

Jira does all of those (including multiple workflows).

Choosing between Rally and Jira is a hard choice, Rally is very good, especially for PMs, but Jira is a lot more flexible - if you're in a large organisation, you'll find Rally gets used for development project stuff, and works well (including some test management). You'll find Jira is used for the same, but then ends up being used to handle all sorts of other stuff - change control, risk management, helpdesk, devops, and even things like to-do lists and asset tracking.

Thanks so much for providing these informations.

Thank you for providing this information.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,723 views 17 21
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you