Marc -Devoteam- Community Champion

Hi @Peter van der Burg I can't explain this as well. I can't see this request as a feature or a Bug. You could raise an issue at Atlassian Support to have them look at this and see of this is a bug or as by design.

Hi @Simon Völk This field can't be cloned, with the checklist options by the Jira ootb clone option. You can make an API call to set the checklist after the issue is cloned or create an automation to achieve this. See the documentation of the app how this can be done via the API.…

Hi @Simon Völk Welcome to the community. Is the checklist option based on 3rd party app? Does the documentation of the app have an API option?

Hi @Adrien Lesueur Go to you required request type, and in the request type on top you will see the option "Workflow Statuses" You will have to apply this to all relevant Request Types individually, this can't be managed on a higher level.

Hi @Spencer Hudson No it is not possible to this macro's format.

Hi @Andre van Rossem This is not possible without a 3rd party app, look at the app xporter.

Hi @Adrien Lesueur Yrs, you need to specify the same name for the status not to be seen visible, and the will not trigger a notification. I mentioned this, and the KB provides this solution as well.

Hi @Peter van der Burg As I mentioned, the board is not on the project BZN , but on project KB. Change the location of the board.

Hi @Andreas Kroschel This app seems to been developed by Atlassian Labs. Atlassian Lab apps are not supported and can be removed if they don't server a purpose to Atlassian. Best is to reach out to Atlassian Support on this one. Any yes you might be required to do this, by moving the Jar from host to host, as it seems that…

Hi @MAHAMMAD AZEEM Can you provide a screenshot of the issue (all details) An provide details on the workflow transition you are trying to execute.

Hi @Peter van der Burg Please show the configuration of your board via a screen shot

HI @Dilip Why are you providing information based on the DC api? The cloud API doesn't allow authentication by username/password, only API token, also for the API version 2

Hi @Peter van der Burg Welcome to the community. Is the board on project BZN or on another project, see board settings of the project. The board needs to be on the project BZN to have the timeline view to work.

Also Service Accounts can't execute towards all API endpoints yet.

Hi @kevin defoi You are not clear, you mention you are on DE, but the API endpoint you provide is from the Cloud API And also the service account option doesn't exist on DC., this is a Cloud only option. So it seems you are on Cloud. As the endpoint you are trying to use is deprecated, its place we are introducing two…

HI @Dilfigar Gouveia Welcome to the community. Are you using Atlassian Guard, then view the existing policies or create a new policy where MFA is not required, then add the user to this policy. Steps for an Administrator to take: * Log in to Atlassian Administration: Go to admin.atlassian.com and select the organization. *…

Hi @dwike_aprilia Adding yourself as space admin will not grant you permissions to restricted pages. You will need to find a Confluence user with access to the page, to provide you permissions. Only if you are on a premium subscription you would be able to grant yourself access to a restricted page. See…

Hi @fernando perez plaza Welcome to the community. This community is an open public form, related to Applications developed by the Company Atlassian. I don't see nay relation to such an application in your request, is there any otherwise you might be asking a question in the wrong forum?

Hi @Anima Gupta Welcome to the community. In Jira DC there are no Team Managed projects, all projects are "Company managed" Team managed is a Cloud only feature, this terminology is also only related to Cloud.

Hi @kevin defoi Welcome to the community. What call are you making, and are you on cloud or DC? What if you use an basic authentication? https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/ 

Are all related tickets in the same project, if so what are the differences in a ticket visible and a ticket not visible?

Hi @MAHAMMAD AZEEM Check for any conditions or validators that might are present on the specific transition in the workflow. Or it could be that issue security has been setup on the project and the security level set on the issue prevents you from accessing it.

Have all related tickets have been populated with the correct organisation value?

Hi @Rutuja Sadul Welcome to the community. Check this article from the scriptrunner documentation https://www.scriptrunnerhq.com/help/example-scripts/basics-create-project-onPrem Otherwise reach out to their support for further input and help. Other solution is to use the API,…

Hi @Jonathan Centeno If you have configured organisations in your service management project then customers in the organisation will be able to see all issues associated with that organisation if the organisation is included on the issue. You can also change the default value for whom the ticket is shared with from being…

Hi @Matteo_Miele Welcome to the community. It seems the account you login with has no JSM agent license assigned. Check if your account is set to be an agent in JSM.

Hi @Davide Doviti Please provide screenshots, what type of project is this? And as I mentioned, check the permission scheme on that project. In the People section ,you can be granted the administrator role, but is this role mentioned on the permission scheme on that project on the permission project administrator A user…

Hi @Lina Xie Welcome to the community. Can you provide more context, what actions are you performing? A pie chart is on a dashboard is this the default pie gadget ootb or from a 3rd party app. HTML 410 relates to a gone status code, this means that the resource requested was once available in the past, but it has now been…

Hi @Shahbal Ehsan I agree with @Matteo Vecchiato . Also I would ask the question, why do you require a 100 projects equally? Otherwise, create API calls to create identical request types in a new JSM project, you created with a shared configuration. But my question still is as above, why?

Hi @Prasad Bonthu @Matteo Vecchiato has valid options, you could also use a lookup table in automation to store the tokens