Hey community,
is it possible to configure that customers from the same organization can change the status / transition of an impediment in the customer portal which was created by another customer (from the same organization?).
Right now it is only allowed that a customer can change the status of impediments which are created by himself.
For Example:
Customer A from Company Z creates impediment.
Customer B from Company Z can change the status of this impediment created by Customer A.
Thank you for your replies.
Cheers
Lars
Hi Lars,
In our server instance, as long as the request has been shared (e.g. via an organization) with another customer, that other customer can transition someone else's request. You could restrict that with conditions in the workflow to say only the reporter can transition for example.
Cheers,
Susan
Hi Susan,
thanks for your reply. I just checked that, I do not have set the condition, that only reporter can change the status :-( So that is not the problem.
Its strange, that the non-reporter (customer of the same organization as the reporter) can see the buttons to change the status in the customer portal and he also can click the button so the pop-up appears where you can write an optional comment. But as soon as you click accept, nothing happens...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, please check you JSD version, if its lower then 4.4.0 then upgrade it.
There is a known bug with unwanted behavior in case you revoke Modify Reporter permission for customer portal in older JSD.
See https://jira.atlassian.com/browse/JSDSERVER-6402 this is only one of many usecases affected by the bug.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, please check you JSD version, if its lower then 4.4.0 then upgrade it.
There is a known bug with unwanted behavior in case you revoke Modify Reporter permission for customer portal in older JSD.
See https://jira.atlassian.com/browse/JSDSERVER-6402 this is only one of many usecases affected by the bug.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.