Mikael Sandberg Community Champion

You would need an app for this, Jira natively do not have a feature that would allow you do this. If you search the Marketplace you can find apps that does exactly this, for example Configuration Manager for Jira and Project Configurator for Jira.

@carlos_marin your guess is as good as mine why Atlassian decided to do it this way. My guess would be that it was a security decision, I found this request JRACLOUD-32353 that indicate that that is the case. My guess is that this will change, there is now an experimental endpoint for workflow creation.

No, you are getting the merge checks wrong. Take the minimum successful builds for example, this is based on a setting on the pull request. This setting can have inProgress, successful or failed. But if a commit that is part of the pull request do not have this value set the merge check is ignored. Same thing applies to…

Are you doing builds on the other branches too and report the build back to Bitbucket? If not then you are good. At my previous job we were doing builds on the integration branch with the merge checks enabled for 1 successful build and that all tasks had to be completed. But we had other feature branches too, but since we…

Okay, so you need to configure your merge checks to only allow a merge to happen if you have at least one successful build. In Jenkins you have to use the Bitbucket build status notifier plugin in order to control this. Once you start a build it will notify Bitbucket that a build is in progress, and once finished it will…

That’s expected. Unless you are the reporter, a request participant, or part of the organization the request is shared with, you will only see requests you submitted. As an agent you can see all the requests from the agent queue.

The portal is the only place they will be able to see their requests and interact with them. This is what the customer sees if they go to the portal and select Requests: Obviously they would see their request in here (my requests are empty because I don't have any open ones in this test project). The only thing the…

Users that are set up as service desk customers will only be able to view and comment on the requests via the portal, this the default behavior. Even if they have access to Jira they will not be able to see the JSM projects from within Jira unless you give them access to do that. 

Hi @pat_alt_non-use, Welcome to Atlassian Community! There isn't an integration between Sourcetree and Jira, see Sourcetree as your GUI for Git. But you will be able to use smart commit comments in Sourcetree and the integration between Bitbucket and Jira will pick that up.

Hi @Rahul, Welcome to Atlassian Community! The documentation you are linking to only applies to Bitbucket Cloud, and based on your screenshot it looks like you are on Bitbucket Server/Data Center. Here is the link to branch permissions on…

Hi @foysal kobir, Welcome to Atlassian Community! Jira Cloud do not have example data, that is only available on server.

Your draft should have been saved, if you click edit on the page will it show your draft then? 

I also saw that Formidable form integrates with Zapier, so yes this can be done since Zapier integrates with Jira.

It looks like Formidable form allows you to send REST API calls, so this should be doable. Just note that the REST API for JSM only allows you to create a request, it does not allow you to update one. In order to trigger the email from JSM to the customer they have to be added to your project first.

You can set up your JSM project to allow external users to send email to it to create a request. One way of doing it is to add the external user as a customer to your JSM project. Under customer settings you can configure how your customers can send email and use the portal.

Hi @John Dooley, Welcome to Atlassian Community! Did your repository already contain the files that you want to ignore? 

Hi @michael Bergermeister, Welcome to Atlassian Community! You could always try and roll back to a previous version of the app by following the steps outlined in this troubleshooting guide, Downgrading an Add-on to an Earlier Version.

This is also a good page to check out to see how fields, screens, and schemes works together, Project screens, schemes and fields 

Hi @michael.tovar, Welcome to Atlassian Community! You cannot dynamically add new fields to the screen when you create an issue. The fields that you see has to be added to the screen used for the create view. See Manage issue screens for more information. 

Hi @Alex Caron, Welcome to Atlassian Community! If you go into the detailed view of the issue you can log your time by clicking the three-dot menu up in the right-hand corner and select Log work, that will bring up the screen that allows you to enter your time.

Hi @demetria, Welcome to Atlassian Community! In order to create a classic project (or company-managed as it is being renamed to) can only be created by users that have Jira admin access, so you would have to add the user to your admin group for Jira in order to allow them to create the project. 

Hi @[deleted], According to this post, An update on next-gen projects customer feedback – March 2021, the team will work on it in the next quarter. There is a request that you can follow to see the progress, JSWCLOUD-17434 

Okay, you have to select which template you want to use. Classic project (which is being renamed to company-managed project) allows you to share configurations between projects, like workflow status, fields etc. Next-gen project (is being renamed to team-managed project) is a fast way to get started, but limits you what…

Up in the left-hand corner, right underneath the project name, does it say Service project or something else?

Hi @JC, Welcome to Atlassian Community! Deleting a space is permanent, and it will delete any pages that was on that space too. The only way to recover those pages would be to restore the space from a backup.

It should show up automatically if you have created a service project. If you go into the detailed view of the request you should see this

Okay, then all you have to do is create a new project and select one if the Service project templates

You would need a Jira Service Management subscription in order to set up a project using one of the templates. 

Hi @Gustavo Juarez, Welcome to Atlassian Community! Internal comments are only available for projects that are set up using one if the Jira Service Management projects. Jira Software projects do not have this feature.

Hi @Tom Williams, Welcome to Atlassian Community! You have a couple of options to do this. One is to add the approvers field to the request form and hide it and set a default value. This works if you want all your change requests to have the same approver. Another option would be to use Services (if you are using the ITSM…