Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>I still don't understand the strangehold JIRA has on some clients.

- Integrations with things like the source code repos, incident management systems, confluence or other wikis, Slack, etc. Moving away from Jira creates a bunch of dead links.

- Internal dependence on complex workflows and state transition rules that are implemented in Jira.

- Various very customized reports that leaders depend on to make decisions, despite the often dubious value and/or accuracy.



Many years worth of source code filled with comments like

    // if we don't toggle bit 7 here 10% of transactions will fail on Thursdays
    // see JIRA issue BIGPROJ-12654 for detailed discussion


When we migrated away from JIRA, we scripted it such that the JIRA issue numbers were recorded in the newly migrated issues exactly because of things like this.


Having migrated bug systems for very large, very old code bases before, it's pretty easy to make the URls and links like this still go to the right place.

This is actually the least difficult thing, i would say ;)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: