The purpose of this thread is to continue the conversation from the 2022.3 Release Workshops on June 28 and 30, 2022.
Thank you to everyone that participated! We'll add more follow ups here as we research some of the questions that came up.
There were also some Innovation Lab ideas discussed, so if you've added any (or found relevant ones), feel free to share them here for others to review and upvote.
Attached are the slides and an MS Project export of the release project template that you can utilize in your own instance to prepare for releases.
We hope you can use this space to connect with one another and build your community!
Leslie, @Cynthia Boon‚ and the Customer Success at Scale team
Topics help categorize Community content and increase your ability to discover relevant content.
Could you provide the template in XLSX format please?
Also, the link to the recording in the after webinar email starts the meeting rather than triggering the recording. Is there another link to access the recording? I had to leave early and would really love to hear the rest of the conversation.
Thank you so much for reaching out to let us know! For anyone on the 6/28 workshop, we've sent a new link to the recording. Apologies for that mix up!
Also, I know we chatted via email, but for anyone else looking to utilize the MS Project file here- you'll want to go to Projects > click the "New Project" drop down > select MS Project and upload the file.
On today's session, we talked a bit about how to help requesters get to the resolving object, and not the issue they input. There are a ton of different ways to handle, here's one idea:
Has anyone else found a way to help requesters find the right place to make updates?
Hi all! We also discussed yesterday the common frustration of people commenting/adding docs/etc. on requests/issues that have already been converted. I've submitted an Innovation Lab for an idea to have these be disabled (not deleted) after they are converted, with only admins being able to edit the issue (or maybe a select group of users). Please help upvote this : )
Project Header customization
As a future release improvement, I think it would be nice to have 6 or possibly 7 project header fields. I wouldn’t want to lose any of the existing 5 fields (project owner, percent complete, planned completion date, status and condition). It would be really beneficial to have project reference number as the 6th header field. Currently, we ask our project owners to add the project reference number in the project title manually. As the 7th field, it would be nice to have the request (“This Resolves”) field.
I have posted this as an idea. See link below.
If you see the value in this improvement, please vote for the idea.
Do you mean adding "This Resolves" field as one of the five header fields? If so, I am aware of that. My idea is more about the field space for 6th and 7th items (rather than current max of 5 fields).
Gotcha. You mentioned would be nice to have that so was making sure you saw it!