-
Suggestion
-
Resolution: Won't Fix
-
Low
-
None
-
None
I would like to see Jira Ops as a self-hosted option, and I'm probably not the only one.
While I do understand that Jira Ops has to be an always-online solution (due to Incident Management), it simply does not fit with our (and probably many others') setup, as we have everything on-premises.
Thanks for your interest and feedback on Jira Ops.
We are currently developing Jira Ops as a cloud-only solution, and don't have any plans to build a Server or self-hosted version. In the long term, we will reassess this once Jira Ops is successfully established as a product.
There are two main reasons for this:
- Jira Ops has bi-directional integration with many other cloud-only products for key functionality, like Opsgenie for alerting, Statuspage for customer communication, and Slack for team messaging. We will continue to enhance these in ways that are challenging to support in a self-hosted environment.
- As an incident management solution Jira Ops is ideally run on infrastructure not managed by your company, so it can stay up when your systems go down.
So for the moment, we have closed this issue as "Won't Fix" and recommend voting for features like JOPSCLOUD-38, or raising suggestions for other Server integrations, which will be considered and prioritised where this is sufficient customer interest.
- is related to
-
JOPSCLOUD-38 Support linking to Jira Server for follow-up task tracking
-
- Closed
-
- mentioned in
-
Page Loading...