![]() Also, it will ensure that users from other groups won’t be able to see this metric even if they’re participating in the request. SLAs – some user groups may require to view the progress in the realization on the request, so displaying SLA measurement to those specific groups may be a good idea.the budget for a hotel room, we can make the most expensive option to choose available only for the directors options – if we have a field in which the requester needs to define, i.e. Add a comment 3 Answers Sorted by: 13 The comment field is not returned by the searchissues method you have to manually state the fields that must be included by setting the corresponding parameter.Click Comment to add the comment to the requests. Click the box beside each request you’d like to comment on. Add comment Get comment Delete comment Update comment. only those who belong to corpoplanet-directors user group may share the requests with other users and view the request participants To comment on multiple requests: From your service project, go to a queue that shows all the requests you’d like to comment on. Contribute to lesstif/php-jira-rest-client development by creating an account on GitHub. fields – similarly to request types, some fields should be available only for those user groups that have the appropriate authorization to access them, i.e.the interns won’t even see this request type when browsing the service desk For instance, the higher-ups in the company should be able to ask for a business car or more valuable hardware. ![]() request types – the same goes for the request types.This will also work even when an external customer knows the link to the internal portal because they will be blocked from entering it Access issue comments through the parent Issue object or the JIRA objects. These are available for use in release notes, and will be visible on. These sessions will apply to all subsequent calls to the jira.client. user emails in source help desk and Jira Service Management are an exact match service desk teams have access to the target project in Jira Service. For example, if we have customer portals for both external and internal users available in the service desk, we should ensure that only our employees will have access to the internal one. Automatically add links to Jira issues in your Octopus releases and deployments. Customer Portal – seeing as not all our users need to see some Customer Portals, we can limit their visibilities to only those who should have access to them. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |