Marc -Devoteam- Community Champion

Hi @Rafał Skrzeczkowski What kind of API token, regular or a scoped token? What are you rights on the JSM project?

Hi @Sally Lopez _CSB014_ Can you show some screenshot(s)

Hi @Abilash Look at the notification scheme used on projects? Or is that not what you are referring to, then please provide more context to your question.

Hi @Radek Dostál In a sese correct, but Behaviours won't work from a customer portal side. If you are on the portal an creating a request a behaviour won't work. Behaviours work from the agent side in the project, as that is creating a work item in the regular way.

Hi @sdotwang Welcome to the community. Check on the approval in the workflow if the current reporter is no excluded to act on an approval.

Hi @Rafał Skrzeczkowski Please show a screenshot of the user used from overview in Administration User Management? And also a screenshot of the permission this user has in the JSM project? The API token used, is is a regular token or a scoped token?

Hi @camila_souza You need to be project admin and you will need to be granted the agent license in User management in the instance administration.

Hi @AdnanFakhar Training Material Yes, that's exactly what I mean. You can also see that at the API endpoints that no Granular options are available.

Hi @Sally Lopez _CSB014_ Welcome to the community. What are the sources of your plan, project, board or filters or a combination? Are the statuses used, or not used in board columns or excluded in filters, if boards and/or filters are used as sources for the plan?

Hi @Felipe de Almeida Toigo @John Funk is correct here. Measurement is the day mentioned and the operator, if you want to include the 21st, you need to use the operator <= or < 2025-10-22"

HI @Prabakar This should be possible from instance to instance, you will need to be org admin in both instances, as I can do this. You could try to make a full backup of your site and create a new site on the other organization, import the backup and then move the data from one site to the other. Use the 30 day trail…

Hi @camila_souza Request Types are a feature of a JSM project only. Yes, forms in JSM projects need to be linked to a Request Type, as these are used on a the JSM portal

Hi @mierdatutis mi Welcome to the community. What is you exact question? The 1st API call shows what data will be imported in the execution, and the 2nd call shows what the current status of the import is.

Hi @Stuart Carter They can add a user on the project in People & Access and grant them the role "service desk customer". The role "service desk customer", based on a project with default permission scheme, grant this user or group access to the customer portal when logged in. Also from one of my earlier comments: Invites…

Hi @Musthafha Sayyad Welcome to the community. Behaviours can't be used on a JSM portal, this is only for agent side. You could use the app Proforma forms to create forms for portal requests and make use of conditions in a form based on choose options Also context options are based on the issue type, not on request type,…

Hi @Andrew Griggs Welcome to the community. Indeed User Picker, for multiple user fields are not supported in a Plan. You could start using Teams, teams can contain multiple users and a Team can be set on an Epic. Als see open feature request, JSWSERVER-25122 

Hi @Steve Farrand As @Alex Koxaras -Relational- mentions, what are the goals you defined in the referenced Time to Resolution SLA?

Hi @Aleksandar Salevski Make sure the user you want to use for this connection is opted out for 2FA, this can't work with 2FA, as the API for on-prem installations can't use 2FA for a user.

Hi @Timothy McKay If my answered help solving you question, please accept my answer as a solution. Cheers

Hi @Kelwin Peralta As mentioend by me and @Olha Yevdokymova_SaaSJet The fields that are hidden, are on the request, but not on the screens used by the work item types for the request. These fields need to be assigned to the screens of the work item, to be also visible on the request type that is based on the work item

HI @田中優貴 Based on your follow-up question, this can only be achieved by 3rd party app from the marketplace, there is no ootb option for this.

Hi @Boyan Iliev Reviewing, you log actin shows that the variable contains a ";" behind the account ID, this needs to be removed in a way, as this is not part of the account ID.

Hi @Melissa Shandy Welcome to the community. You can set a default for the field that is not a number. In your automation, do a re-fetch action before doing the edit action on converting the number to currency. Then you will need to have a text custom field where automation can set the number value as currency So this…

Hi @Pasi Vepsä You need to export the full space, not a page. Within the space admin, in the general section, there is an option called "Advanced Options" Then you will get the XML optoin.

Hi @Boyan Iliev Have you confirmed your variable does not contain any leading / trailing spaces? I think this might be the issue. You could try the following option in the edit {{loopFEUsers.trim}}

Hi @Pasi Vepsä So you have 2 cloud instances. To cancel a Confluence, see https://support.atlassian.com/subscriptions-and-billing/docs/cancel-a-subscription/ Migrate spaces, by exporting them, as XML (to import them, if need in another instance of…

Hi @Aleksandar Salevski You would need the following, access on the DC instance? Can the Cloud instance reach the DC instance? Use oAuth or basic authentication option, to connect to the DC API, https://developer.atlassian.com/server/jira/platform/security-overview/ These are pre-conditions that need to be true. Then in…

Hi @sunil manocha Has this field been created in a Team-managed project or via the Jira administation? Custom fields created in Team-managed projects, only relate to that project, as a Team-managed project is a container.

Hi @AdnanFakhar Training Material The Software API has no granular scopes, so you can't use a scoped API token with the software API endpoint.

Hi @timothy_higgs_extern Create your automation like this: * trigger: issue created * smart values condition: check if the parent label is present* first value: {{issue.parent.labels}} * condition: contains * second value: TIN-DP-PLATFORM-WORK * action: edit issue select the labels field from the dropdown, and at the right…