Mikael Sandberg Community Champion

Hi @vats12, Welcome to Atlassian Community! You cannot set restrictions on the task so only specific users can resolve it. I looked to see if there was a request to have this feature added, but could not find any, so the only thing I can recommend is that you go and add a new suggestion here. 

@Luis, You should probably create a separate question for this, and refer back to this one. There apps in the Marketplace for inventory, if you have access to Insight (you need Jira Service Management Premium) you could use that to keep track of inventory.

The picture only shows the headers from the csv file. When you do the import you will be asked to map these headers to a corresponding Jira field. Make sure that you are mapping a header to the reporter, if that is not done Jira will default back to set the reporter to the user running the import.

In the JSM project, if you look on the left-hand side you should see Channel (if you see Back to project at the top, just click that to see it), similar to this: If you click on it you should see a link to the portal. The URL is something like https://your-instance.atlassian.net/servicedesk/customer/portal/1

Hi @Tej Dewangan, Welcome to Atlassian Community! You can accomplish this by setting up issue security, you can then control which issues users have access to. Have a look at this KB for more information on how to configure issue security. 

Welcome to the group! If you have any questions or need help coming up with arguments why to choose JSM just let us know.

It sounds like you want to set the resolution when moving to done, so when an issue is in that status it will look something like this: In order to do that you will have to add a screen to the transition to Done, and on that screen you need to add the field Resolution.

Did you update the permission scheme that all your other projects are using? It sounds like you didn't and that is why the external user can still see those. When you want users to only have access to specific projects you have to make the permission change to all projects, not just specific ones.

Hi @asanch04, Welcome to Atlassian Community! Unless you add the issue key to existing issues into your csv file, Jira will import everything as new issues. If the issue key is present in the file, the issue will be updated with the information in the file. 

Hi @Minnie Cui, Welcome to Atlassian Community! You can do this using automation. Create one that looks for the specific component when the issue is created and if so, then add the user to the request participants field. Something like this should do it:

Correct, plugins are called apps in the Atlassian world.

Another thing that you may want to try is to reselect the status in the if condition, I noticed that sometimes the library automations will not work unless you make a small change to them.

Unfortunately there is no such integration between Bitbucket and YouTrack. The only thing I can recommend it is to contact JetBrains and see if they have any plans on creating an app for Bitbucket.

How about using a scheduled automation for this. You could send a web request to Get users from group endpoint and then use the result to notify the user. 

Hi @Vicky Carrillo, Welcome to Atlassian Community! You can do that if you configure the permission scheme being used by all your project so browse projects is based on a project role instead of the default which allows everyone logged in. This will allow you to delegate who have access to project to the project lead. This…

Does your mapping have an entry for the reporter?

The user object will show if the account is active, inactive, or closed. This is a new attribute that was just added to the user object, see the announcement here.

Hi @mfilippo, Welcome to Atlassian Community! It looks like YouTrack can integrate with Bitbucket the way you looking for, as long as you have a version of YouTrack that supports it. Have a look at their documentation on how to set up the integration. 

My brain was on auto-pilot this morning. You are correct, it is the reporter that will be set to the user running the import unless you have a column for it in the csv and map it to the reporter in the configuration.

Correct, the only way to get the information is to have it in your csv file.

If you do not map a column in your csv file to the assignee field, Jira will automatically set the reporter to the person running the import. What is being imported is controlled by the mapping configuration.

Hi @Greg Gibble, Welcome to Atlassian Community! You need a column in your csv file for the assignee reporter (their email address), and then add that to your mapping configuration in order to set the assignee to someone else then you.

Suspended means that you currently do not have an active subscription for that app, this happens when you disable the app.

It looks like it is this app, Sum it up! When I look out our subscriptions apps that we have shows up with the Atlassian logo instead of the actual app logo.

It is not the last commit you will have to rewind your history, either by using git filter-branch or the BFG utility. Have a look a this KB for instructions.

Hi @Salazar Comunicación, Welcome to Atlassian Community? Removing the files locally in your repository will not reduce the size, since Git keeps a full history of your repository. If the commit is the last one that you did you have to revert that commit/push. If it is not the last commit you have to remove the file from…

Hi @[deleted], Welcome to Atlassian Community! You could do this if you check the Share configuration when creating a project. Take a look at the Create a project that shares its configuration with another project section here for more information on what is shared when you do this.

Currently escalations are manually done based on an application directory we have in Confluence, we only use automations for specific requests, like application access and peripheral requests. The process for application access is fully automated for 60 some applications using a combination of Insight, automations, and…

No, it looks like the session was only available for a short while for the team tour. You may want to reach out to Scott Valena via LinkedIn and see if you can get a copy of the presentation.

Currently we have 12 agents (3 Tier 1, 2 Tier 2 & 7 Tier 3) and in the past year we have had close to 12k requests. When we started using JSM a year ago we only had 6 agents.