Currently we have an organisation setup on jira service desk (cloud) with sharing setup so people within the organisation can see issues logged by others within the organisation.
This workflow also has an approval stage before tickets are worked on.
Currently only tickets that have passed this approval stage are viewable by others within the organisation.
Do we have any way of allowing these issues awaiting approval to be seen by all in the organisation.
this seems odd to me TBH. My experience is that if issues are shared w/ the Organization and assuming I add myself as a participant then I should be able to see all Open issue and Open includes 'not yet approved'. i'm perplexed as to why a customer would not see non-approved issues. can you verify that a customer that cannot see these is actually a request participant?
They are a member of the organisation and the organisation is a participant.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
note i have edited this as my original response was not clear or precisely accurate...
to be clear just because an issue is shared w/ the organization a member of the org will not receive notifications for an issue unless they choose to participate. Not if you have enabled the "Organization added" under Customer Notifications all customer in the org will receive the initial issue created notification but not the subsequent notifications. However, as a customer in an organization I can see all issues shared w/ the organization by using the “All” option in the portal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I see the following under my organisation (as do others in the organisation).
Because I am the approver for the workflow I can see this under the approvals.
When I approve an item it only then adds my organisation to be shared with.
This is despite the organisation being included on the creation form.
I've checked the workflows and they are not altering who it is sharing with on the transition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Discovered the issue it was a PICNIC issue.
Turns out I forgot to hide the sharing field and the users had removed the default share with organisation as part of the entry form.
I hadn't considered users!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I second that seems odd? I don't know of any functionality that "hides" the request from the organization based on approvals? It's either shared up front, or at some point onwards, but the sharing is not dependent on status/steps
Curious?
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.