Marc -Devoteam- Community Champion

Hi @임동규 No, this is not related. But in Jira no users can have anonymous access, they need a license. The mentioned documentation doesn't mention anonymous users

Hi @Toby Hunter Set the term as searchTerm="Email" Or use the cloud platform api to search issues /rest/api/latest/search/jq?jql=project = <project ket of jsm project> and summary ~ "Email"

Hi @Namrata Bhomkar No you can't make fields mandatory for request created by email. If the request can only be raised via the portal, then just set the field to be mandatory in the request configuratiot. You could create an automation to set this field, but then the question is how. How would the automation know what…

Hi @Scott McDonald Issue security levels can only be set to roles, groups and users. In the case of responders to create alerts, you need JSM premium subscription and see the incident management section non the space settings.

Hi @Kevin Vancrutsen Your rule trigger should be based on a manual or scheduled trigger. Then do a lookup of issues where field department is option A Ten branch over the found issues and within the branch do an edit action where the field Department V2 is set key = <key of the related object from assets> Repeat these…

Hi @nikki Yes you can. You could search for all the tickets and then do a bulk update and move the issues to the new Jira space. Or you can export them and import them via csv, but as you are just creating a new project the bulk move option would be the most logical

Hi @Fabian Burkert Do yo mean every page created by an owner, an owner sets a label on the page? Then you should be able to query on this label.

Hi @Genevieve Riffe You can rename the Epic work type as suggested by @Trudy P Claspill Or you would need to revert yourself to 3rd party apps from the marketplace, for custom hierarchy options. The parent / child relation is only on Epic level, so if this is your wish, best is to rename the Epic work type.

Hi @Mikel Whipple To do this, you first need to add an extra user attribute on the user object in the assets schema. This way you can link the user object to a real Atlassian user. See there documentation on how this can be done via…

Hi @Kevin Roe Go to the JSM space, select the Customer option. In this section the JSM space customers and Organizations can be managed If this is not the case, make sure the feature "Customer and organisation profiles" is enabled in space settings, feature option.

Hi @Scott McDonald The request participant field can only hold user or mail address, no groups or teams. To add group member as request participants, see how-to-add-group-members-as-request-participants There is also an open feature request; JSDCLOUD-1268 There is no API endpoint get the responders of an alert. You can use…

Hi @Kevin Roe On the JSM space have you added the organizations? I don't think you have. You are no globally managing the organizations, but you will have to add them in a JSM space. They are not by default used by any JSM space.

Hi @Abhinav Ingle is your use in the role Service Desk Team and in Atlassian administration on accessing your user, do you have the agent role?

Hi @Genevieve Riffe Welcome to the community. You can't the ootb hierarchy can only have levels above Epic or on the same existing level, but there can't be a level added in between the ootb hierarchy.

Hi @Fabian Burkert You can use the API to get all pages. See; api-pages-get in the call you can specify the space id, to get the pages from a single space. example https://<cloud-name>.atlassian.net/wiki/api/v2/pages?space-id=<space-id number> Page owner will be returned by account id, as based on GDPR not direct names or…

Hi @דניאל שוקרון This question you should raise with Gliffy support. https://marketplace.atlassian.com/apps/254/gliffy-diagrams-for-confluence?hosting=datacenter&tab=support 

Hi @Wellington Batista da Silva What was the issue?

Hi @Admin dcode To answer your questions. * Yes, if you start payment again * Yes they do * You need to contact billing

Hi @Canaan Gardner The API call option you are making suggests you are using a service account and an API token related to that account. The above call to api.atlassian.etc... requires a service account and api token of that service account The one that is working is if the token is based on your user in Jira.

Hi @Asha What are the security restrictions, you can set a permission scheme based on groups instead of space roles. This will make the access section in the space permissions useless, as a prject manager adding users or groups to roles, won't have any effect. Use an Work Item security scheme, and create an automation rule…

Hi @Hagit Nagola Shaham Or the time tracking field is not present on the screens used by the work type or its a permission issue. So both @Rohit Utukuri and @Rik de Valk _Brainboss_ have a valid poiunt. It can be one of them or even both.

Hi @Andy Christley This is not possible. JQL finds issues and this clause can be stored as a filter, you can use the filter in another JQL, but not in a column, columns show the value of the field in the found issue Example: project = xxx and filter = <name-of-a-filter> Then you can use the JQL of another filter in another…

Hi @rob_brown Your JQL finds 6 issues, but you also have the checkbox enabled: "Only include work items that have changed since the last time this rule executed" This means the JQL finds 6 issues, that are conform the search query, but if those issues have not been touched (updated) since the last run of the rule, these…

Hi @Antoine MAIER I think then it's best to reach out to Atlassian Support and see how they might help. (You will need to hold n admin role to raise a request, minmal is Jira admin) Please list the solution if they provide one

Hi @Antonia This is not an option ootb, you could do this with a scriptrunner behaviour if you have the script runner app. If you set the fields mandatory on internal creation, and not on the request, they are still seen a mandatory, this as the issue is created on the field config used, not based on the request type…

Hi @Payne This is a field in your instance, if it doesn't serves any purpose remove it from the screens. If you add user groups in User and Roles, then you can share the issue with this group. See; Share requests with groups from the issue view in the linked page.

Hi @Antoine MAIER Did you replace <name of the custom field> with the name of your field?

Hi @Antonia If you create work item via request types that are connected to email, these request types can't contain required fields. Requests created via email only summary and description can be used, no mandatory fields, as from an email these fiedls can't be filled.

Hi @Wellington Batista da Silva What does it say at "Acesso ao aplicativo"? What are you roles at "Funçoes" at the project access? If you have a Jira license /rest/api/3/project/search should give you results, if not it's permission issue

Hi @Annu Satpute I think this is now under the marketplace apps section in Jira, called oauth credentials https://<your instance name..atlassian.net/secure/admin/oauth-credentials See also; https://support.atlassian.com/jira-cloud-administration/docs/integrate-with-self-hosted-tools-using-oauth/ Or on what I'm reading, you…