Mikael Sandberg Community Champion

Hi @Ameer A, Welcome to Atlassian Community! Yes, it is possible and you can do it using the branch rule related issues. Something like this should do it:

You cannot do it using Automations, but you could probably do it using a post function in the workflow and Scriptrunner.

Hi @Khaye Garduce, Welcome to Atlassian Community! What is your use case? Do you want to move completed issues in a Kanban to a different project? 

In order to enable anonymous access to a space you have to enable the anonymous access under global permissions, you can then enable anonymous access to individual spaces.

Hi @David Roy Morin, Welcome to Atlassian Community! Try using {{issue.epic.Epic Name}} in your search. 

You have to check if a parent page has the view restriction set, and also make sure that your Jira users have access to the space. 

You may want to take a look at JSM Premium plan, which includes Insight, which is an asset management tool and so much more. We use it not only for asset management, but also as an application db that we use to automate access requests to different applications.

You would have to set something up locally that pulls from the remote repository. Git does not keep track of each clone, so you would not be able to do something like that from the remote repository.

All you have do is create a new board and you will be able to create sprints in the new project.

No, issue archiving is not a feature in Jira, you only have project archiving if you are on the Premium or Enterprise plans. There is a suggestion to implement issue archiving, but based on the feedback it would most likely never happen, see JRACLOUD-5843 .

Only agents in JSM needs a license, you can set up your internal users to be customers so that they can submit requests via email without one.

Take a look at the Library, there is a rule in there named "When a comment is added → update the status" that you can use as you starting point. That one changes the status both when the reporter and the agent adds comments, but you could remove the one for the agent if you want.

We used to before moving to a separate tool. This the workflow that we used: Work Management has a template for Procurement that you could use, it uses a workflow that looks like this:

Hi @Ashish Gireesh, Welcome to Atlassian Community! What you see when creating a new project and using the shared project settings is expected behavior. Because you are using the shared setting, this will override the template you selected, and because of that Jira will not know what type of board to create. 

Okay, because your screen scheme is shared you have to be a Jira admin in order to make any changes to the screens. You would have to contact your admin and have them add the field for you.

Hi @John Fitz, Welcome to Atlassian Community! Make sure that the field has been added to the screen that the bug issue type is using. Go to Project settings > Screens and click on the screen used by Bug. 

The license count is based on unique users, so if you have a user that is a member of both groups they will only count once.

You can ignore those emails, they were sent in error. Have a look at Atlassian's status page for more info

Hi @Jan DeFalco, Welcome to Atlassian Community! I use ServiceRocket to integrate Jira and SFDC, and when you add an app to your instance you have to purchase the license tier that is the same as your Atlassian host product. You can learn more about it here. 

Hi @Senda Del Cid, Welcome to Atlassian Community! You need to contact your IT team and they should be able to help you. The community doesn't have access to customer instances. 

Project archiving is only available in Premium and Enterprise plans.

You should reconfigure your board and the filter that it is using. Once an issue hits the right far most column it is considered done and will show up in reports as such. If you leave out UAT and ready for prod from the filter you you should then be able to close sprints normally.

Go to Settings > Projects or Projects > View all projects. From here you locate the project and then click on the three-dot menu on the right and select Move to archive.

Hi @Gloria Phakathi, Welcome to Atlassian Community! You cannot archive individual issues, currently you can only archive projects. If you give a bit more information on what you are trying to accomplish we can give you further advice.

Hi @Suneel Varma, Welcome to Atlassian Community! You could make your automation a manual one, then you can click on Rule execution and it will be listed as an option.

Hi @Rose Randall, Welcome to Atlassian Community! If you select the files that are staged, you can un-stage them and they should be moved to the un-staged section.

@karunt Syncing a branch is not equal to merge. Only a merge to the default branch will reset the ahead/behind count.

Hi @Sebastian Somi, Welcome to Atlassian Community! You may want to add some more information here, are you saying that you have an issue assigned to you with the label Permanent and you are seeing that issue when you run the above filter?

Make sure that the fields have been added to the issue screens, and also check that the fields are not hidden on the agent view layout.

Hi @paul sindoni, Welcome to Atlassian Community! It looks like you ended up here because RazorSync is using Confluence for their documentation. You may want to send your questions to their support, support@razorsync.com