- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2022 12:49 AM
Hello
My company would like to use release management in order to group all changes to implement on a same release.
I’ve checked what exists OOB and there are some things I don’t understand:
If I affect one or more changes through the release screen, then I can see all the changes in the release screen but I can’t see the release number/description in the change screen or in the change table. This is an issue as I would like that the requester of the change can see that the change belongs to which release.
How can we achieve this? Isn’t it OOB to see the release on the change if I have affected the change in the release before?
Note : I don't speak about adding releases in a change request, it is the contrary, each change should belong to one unique release (or belong to nothing).
Regards
Vanessa Heux
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-08-2022 06:52 AM
Hi Vanessa,
As we can see, OOTB this is implemented many-to-many, so in order to do what you want you will have to define a new custom Release field (of type Reference, and Read only) in the change_request table and have it populated via a Flow (or a BR) the moment a new change is added to a release.
Regards.
JP
JP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2022 06:30 AM
What if any, is the intended operational design for this OOTB release module?
