Mikael Sandberg Community Champion

Hi @phil.kibitt, Welcome to Atlassian Community! Boards are using filters to display issues on it, so you should check the board settings to determine what makes an issue show up on either boards. 

If you look at the filter used for your open support issues queue, you will likely see that it is looking at resolution = Unresolved, so if you see your closed requests in the queue it means that the resolution on those requests are not set. You can fix that by creating an automation that sets the resolution, but you…

Create an attribute of the type User, that will link the field Atlassian accounts. See my answers in this thread, https://community.atlassian.com/t5/Jira-Service-Management/How-do-i-import-all-the-users-from-Atlassian-Access-into-Insight/qaq-p/1840277

Instead of using "Story Points" have you tried using the ID for the field instead? It is something like this: customfield_123456. You can get the ID by going to Issues > Custom fields, search for Story Points and then click the three dot menu and hover over Details. The URL will show you the ID, it is the last part of the…

Also, take a look at this thread, https://community.atlassian.com/t5/Jira-Core-Server-questions/Jira-REST-API-Create-Issue/qaq-p/213945

You have to make sure Story Points is on both your create screen and edit screen. Go to project settings and check you screen scheme.

The clue is in the error message. You have to make sure Story Points is on the edit screen.

{ "fields": { "Story Points" : <Number> } } This is all you need to send in the body.

Hi @Katherine Purcell, Welcome to Atlassian Community! No, the Analytics page cannot be configured. I would suggest that you add a suggestion to jira.atlassian.com to have that option added. 

You would have to contact Atlassian support and they should be able to help you get access to your instance

Hi @[deleted], Welcome to Atlassian Community! Story Points is just a custom field so the end point you are looking for is Edit issue.

Correct, the banner in Jira cannot be limited to specific groups.

There isn't a field for the owner, but you could see who have edit permissions and assume that one of those users is the owner (Configure > Permissions). But if the permissions has been changed to just list groups then there is no way to identify the owner, unless you that information in the Description of the plan.

This IQL should get you all the assets: "Responsible Owner" IN ("user1", "user2", "userN") 

Now you have a specific menu for removed issues, and from here you can select to add them back to your plan. Just go to Configure > Removed issues.

No, you have no control over that, those are the options that everyone have using Cloud. You can work around it if you want to use SSO by subscribing to Atlassian Access and connect it to your user provider.

All you have to do is go to the Object schema, select Attributes and create a new attribute that is of the type Users. Here are the Cloud instructions for it, Create an attribute. The Cloud documentation does not reference the different types you can select, but have a look at the one for Data Center, Adding attributes to…

The short answer is no, you cannot limit the banner in Help Center to only be visible to internal users.

You cannot directly import users from Atlassian Access into Insight, but what you can do is set the attribute to be of the type User, that will allow you to associate the Atlassian ID with an asset so you can search assets based on the user.

Hi @Dana Burrows, Welcome to Atlassian Community! I don't know anything about AWS Lambda, but if it accept incoming REST API calls you can use automation to send a web request to it once the request has been approved in JSM. 

It is not possible to change the references to Jira issues in Bitbucket, unless the pull request is open and you change the description field, or comments. Note that Jira keeps track of the old and the new issue key, so even though Bitbucket is referencing the old key, if you click on it you will be forwarded to the new…

I noticed that the other day while updating some of our assets, but once I forced a reload of the page everything was back to normal.

Hi @Elijah Appius, Welcome to Atlassian Community! You would need to contact your Atlassian admin at your company and they should be able to help you.

You can always create a new queue for resolved requests, and your filter should look this: resolution != Unresolved

You would need an app to do that. You may want to take a look at Checkout - Procurement & Asset Manager 

Short answer is no, bulk edit is only for issues.

Hi @Nate Jenks, Welcome to Atlassian Community! You can do this with automation, just create one that takes the information from the different fields and then update the description field with it. Something like this (in this case I take the description field and concat it down to 200 characters and adds it to a TLDR…

The free version of Jira allows you to add new issue types, just be aware that Jira will only recognize the level of Epic -> Story/Task -> Sub-task. If you want to expand that you would have to use the premium version to get Advanced roadmap, or look at adding an app like Structure to your Jira instance.

Any apps that you install comes with a trial period, and unless you end the trial before the end of that period you will be charged for that app. If you go to Apps > Manage apps you should see all your installed apps.

Hi @Anna Comer, Welcome to Atlassian Community! JQL is not SQL, so you cannot create a JQL that sums up the total. Instead you can use the Jira gadgets available in Confluence to show the numbers.