In the end though, don’t worry the managers will get their reports and everyone will at least have there feature box checked (assume you don’t care about Markdown).
In the end though, don’t worry the managers will get their reports and everyone will at least have there feature box checked (assume you don’t care about Markdown).
So bosses want Jira, developers want Github. This is one of those have your cake and eat it too scenarios for both Atlassian and GitHub.
For me its important that it is separate from GitHub for a few reasons:
- having a Jira project means we can easily move issues between projects. This is especially useful for when our support team notices an issue, submits a ticket to our "support ingest" project, and then it can get routed to the correct actual project on the backend. Or when an issue gets misdiagnosed we can move it between projects while keeping a single issue and all the history of it.
- having more complex workflows that allow you to force issues to go through specific steps, trigger webhooks, good fun stuff like that
I really would love a good alternative. Jira has just gotten slower and slower, their UX has gotten worse, and I really would like a good alternative.
However Jira has solid integrations into a lot of places and does a lot of complicated things.
Suggestions?