How do you share change requests out to your change advisory boards, especially during CAB meetings? Our current view looks like this, and the data is very tight and often hard to read. Any change descriptions that go beyond a few lines often go beyond the page and grouping changes together from the same requestor is nearly impossible without lots of scrolling.
Any recommendations would be greatly appreciated
@Tinker Fadoua it's a table within a template page. I'm wide open to alternative methods of capturing and sharing change tickets in a readable and permanent method. We cannot use a filter for audit purposes.
This worked well for us prior to the new Confluence editor.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Based on the information you need for your CAB I don't think there is anything to recommend here.
How about creating a change request issue type add all the columns as fields to capture the information so you can share it during your CAB meeting? then create a filter that you can share on a Confluence page with all the change requests.
Best,
Fadoua
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Fadoua,
Do you have any recommendations on decreasing the amount of information needed for a global CAB? I would love to follow best practices/recommendations, but I can't really find much.
Unfortunately, this list must be static for audit purposes and a filter that is purpose-built to be dynamic doesn't meet our needs.
Thanks,
Mathew
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.