Mikael Sandberg Community Champion

It does, but next-gen projects are different then classic ones, and have restricted functionality. Resolution is normally set using a post function in the workflow, and next-gen project do not have workflows (which is changing). Another option 

Is your project next-gen or classic? Next-gen projects cannot share custom fields, that can only be done if you create a classic project. If you have a classic project and then you first have to add them to the screen used by the project for them to show up. All your custom fields (excluding the ones created in next-gen…

If you go to Settings > Issues > Permission scheme and then click Edit to the right of the scheme you want to rename it will take you to the page where you can rename it and also add a description.

Hi @Yee Frost, Welcome to Atlassian Community! In Cloud you set up the integration after the field has been created. Once the field is created, click the three dot menu and select Configure. From here you can add the filter. Take a look at Integrating Insight with Jira for more information. 

In your automation rule, have you changed the scope to include the Software project? If you created the rule from the JSM project it will only apply the scope to that project.

You could use automation to set the date once the ticket reaches a specific status. As you have noticed, next-gen do not have a Resolution field. In classic projects the resolution date is set when the resolution is set to a value. 

Hi @jesus.bermudez, Welcome to Atlassian Community! The short answer is no, you cannot limit the numbering, as long as the project is active Jira will just add on to the last number used. The only thing you can change is the project key.

Hi @Obinna Okoroma , Welcome to Atlassian Community! Your license key is not tied to the server ID, so you can move it over to the new server without issues. If you want to set up Confluence on the new server first to verify that everything is working you can use the developer license that you have access to and can…

Hi Aaron, Welcome to Atlassian Community! You can only set the resolution to unresolved as part of a post function in the workflow, it is not possible to do it by adding the resolution to a screen. Have a look at Advanced workflow configuration for more information.

One way of doing it is to use issue security. It allows you to set permission on who can view the issue, you could then limit it to only allow the requestor and the assigned agent to see the ticket. Have a look at Configuring issue-level security for more information. 

Hi @Denise Durgee, Welcome to Atlassian Community! You could use a query like this to this: status CHANGED TO "Done" AFTER 2020-10-1 BEFORE 2020-12-31 You can find more information about advanced JQL searches here, https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/

You need an app to do it, the out of the box Jira do not have this feature.

Here is the post Atlassian added to the Trust & Security group.

You can do this if you add Automation, on server there are two versions of it, Automation Lite which is free but have limited features, and Automation Pro. 

Have you looked at JSM and Insight? You could store your inventory in Insight and have it automatically updating based on tickets coming in via JSM.

Can you reach/kick off those scripts from a web request? If so, then you can use an automation rule to initiate that web request.

Okay, so the commands you found will reset your local branch, before you do that make sure that you have saved your commits, if you have any. The easiest way to do that is create a new branch, and then switch back to your master branch and then reset it.

Hi @rihab ayari, Welcome to Atlassian Community! When you get that error when pushing it means that your local repository do not have all the commits that your remote repository does, and the only way to solve it is to do a pull first. You mentioned that you cannot do a pull and merge, could you explain more? Do you get an…

Hi @Christine Fowkes, Welcome to Atlassian Community! Is the new request type using the same issue type as the other ones? If it is assigned to a different issue type then for example Get IT Help you will not see it in the request type list.

Hi @Percy Sanchez, Welcome to Atlassian Community! The way I would do is is to have a transition to Close in the workflow, call it quick close, and then maybe put a condition on who can do this transition. 

Yes, Insights/Analytics is by default available for every user if you are on the premium plan.

Hi @kaimen, Welcome to Atlassian Community. Yes, by default all users have access to view Analytics in Confluence. If needed you can set who can view analytics on your site and spaces. 

That is correct. I have a couple of apps that I have to the same for, one example is the Salesforce integration which is used by one team, but it shows up in our JSM projects which do not use that integration.

Are you using an app to connect to your Git repositories? Unfortunately, most apps do not allow you to configure which projects it should be available for, so you will end up having a reference to them in all your projects.

Bingo!

I would start by checking out the Jira automation template library, it has a lot of examples and links to blog posts that gives you more in depth information. Creating the rule you are looking to implement is fairly simple, just be aware that depending on what plan you are, there are limits to the number of multi-project…

The short answer is yes, you can do this using Automation. I use it to create tasks that needs to be completed when a new employee is onboarding/offboarding for example.

Correct, the folder in Sourcetree is an internal folder and has nothing to do with your windows folders. I wish they renamed it to something like bookmark folder, on Mac it is called Repository group.

@Kotresha B yes, but with restrictions unless you use an app or using the XML backup. If you do not want to use the XML backup to do it you will not be able to get any of the project configuration in the export. 

The local folder is where Sourcetree will store the bookmark of your repository, so you can organize your repositories the way you like it. You can add new folders if you go to your repositories and then just right-click in there.