Looking for a way to change the label postmortem. This is frequently referred to as an RCA but the postmortem label seems to be hard coded in. thanks
Hi @Mike Capone
This is Darryl. I am here to help. 😀
The Postmortem on Statuspage is meant to publish the RCA for the subscribers and the internal team members to understand the incident.
I am not sure about the "label" you mean here. As the screenshot attached below, there is no label existing on the Postmortem report of an Incident on Statuspage.
Please provide more details or screenshots to help us understand your inquiry.
Thank you.
Thanks Darryl. My team was able to figure it out looking at the back end scripts. All good
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for keeping us posted, @Mike Capone !
You and your team are awesome! 😎
Have a great weekend ahead.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mike Capone I'm just finding this, and our organization hopes to do the same thing … are you able to share more detail about how you solved this?
@Darryl Lee the primary request for us is that the name 'Postmortem' is not the language we want to use for end-user communication. We are hoping to publish it under a different title than 'Postmortem' such as 'Review' or 'After-Outage Report'.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Don Rogers,
Thanks for further clarification.
Unfortunately, the term/title "Postmortem" is not possible to be changed in the current design.
We see how significant this is to you and your business, so I have submitted a feature request with the information mentioned above.
The feature request ticket is STATUS-116.
We will keep you updated about this feature request because it doesn't provide visibility to our customers.
Please note that our Product team reviews all Feature Request (FR) together and they prioritize those with higher demand to be implemented first and any FR will take months until is ready since it needs to go through Design, Development, Testing, and rolling out to Production.
We greatly appreciate your thoughts on how we might make Statuspage better; it really helps.
In the meanwhile, we apologize for the inconveniences and frustrations caused by this inadequate functionality.
Best regards,
Darryl Lee
Support Engineer, Atlassian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did either of you find a way to make this work yourself (Mike you noted backend scripts - did you make a change or were you just able to see it was not possible per Darryl's note?)
We also want to change for similar reasons to Don's comment.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Craig CaplanWe did not end up finding a path to implement this, but we continue to want to. Sorry I can't offer anything more helpful!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.