At my company we are working on implementing JIRA as Issue Tracking and Project Management tool. Are there some best practices or transition tips which anyone would like to share.
Do companies hire a consultant or it is easier to do it yourself ?
thanks and regards
I work as a consultant doing the very thing you asked. Implementation difficulty honestly depends on the quantity of issues to migrate (and what software they are coming from), the amount of teams the software is being deployed to, and is also dependent on your knowledge and flexibility of the business process's of those teams. Experts are listed and can be found here: https://www.atlassian.com/resources/experts As far as best practices, it would be too much for me to try and post any of that information here, the options are really limitless. The web documentation is listed: https://confluence.atlassian.com/display/ALLDOC/Atlassian+Documentation
I'd like to add my two cents:
I guess that you are already using some issue tracking software in your company and now you are wondering if you could easily migrate to JIRA. When it comes to that, JIRA has a couple of build-in importers, which will take care of migration for you: https://confluence.atlassian.com/display/JIRA/Migrating+from+Other+Issue+Trackers.
JIRA also supports migration via open-format such as CSV and JSON in case your issue tracking system is not among supported ones.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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!
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