We appreciate you taking the time to vote and add your suggestions to make our products awesome! Your request will be submitted to the community for review and inclusion into the backlog.
We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
When Cireson resolves an IR for an app, provide a summary of it
Adam_Dzyacky
Product Owner Contributor Monkey ✭✭✭✭✭
It's probably not a huge surprise to a lot of people here (in the community) how Cireson portal permissions work with regards to being an Affected User.
As an end user and being the Affected User of an IR/SR, you're able to see all details as it relates to your request. This is no different in Cireson's deployment of their own portal for their own SCSM deployment. It's with this said, many customers raise Incidents about Cireson products that are oft...occas...seldo...I think we can agree some portion are acknowledged as true bugs.
When this happens and those bugs/IRs are resolved, corresponding patch notes for those apps are referenced with only their work item ID and title only. (Example: My Active Work Items patch notes - "[IR51867] MAWI column persistance issue"
Given that other customers can't see other customer's work items, it would be great if the description of that IR (or just some kind of summary) could be published as a bullet point under the respective patch note so that onlookers can evaluate if they are truly experiencing a similar issue before patching, submitting a new IR, and even just understanding what was addressed in further detail, etc.
As an end user and being the Affected User of an IR/SR, you're able to see all details as it relates to your request. This is no different in Cireson's deployment of their own portal for their own SCSM deployment. It's with this said, many customers raise Incidents about Cireson products that are oft...occas...seldo...I think we can agree some portion are acknowledged as true bugs.
When this happens and those bugs/IRs are resolved, corresponding patch notes for those apps are referenced with only their work item ID and title only. (Example: My Active Work Items patch notes - "[IR51867] MAWI column persistance issue"Given that other customers can't see other customer's work items, it would be great if the description of that IR (or just some kind of summary) could be published as a bullet point under the respective patch note so that onlookers can evaluate if they are truly experiencing a similar issue before patching, submitting a new IR, and even just understanding what was addressed in further detail, etc.
5
Comments
THIS.
Then the release notes can have a list of PRs for each bug that has been fixed.
...
Or a single Release Record ID which contains all the PRs?
https://support.cireson.com/Page/e9123c0c-38a6-4ced-9962-f73f49771ce9
Hope that helps