Prince Nyeche - ELFAPP Atlassian Partner

Hi @David Neeley (KVHC38) With 3LO you're given authorization grant, JSM customers are not Jira users, so I do not think you can impersonate such users and I don't think login via REST for customer users even exist. So my suggestion is to have your chat bot as an agent create the tickets for each customer and assign the…

Hi @Keerthana Bhuthala Welcome to community! In order to know the Field type prior to creation, you will need to search the Custom Field endpoint. you can create a function to return a field type prior to creation. From the output JSON it will return the type and searcherKey, which you can use to determine what type of…

If i'm not mistaken, it only has a macos client.

Hi @Ryan Clayton Welcome to Community! Jira Cloud uses AccountId for any user identification this means for you to perform an import, it's either you change those user fields to "email_address" or a corresponding "accountId". Since you're importing from Server, I believe the JSON might be different for the author field.…

Hi @Rolf Lader It isn't possible to merge Atlassian account right now - see ID-240 . However it is possible to perform a swap of Atlassian account following this guide. 

Hi @Amit Anand Welcome to community. In order to perform such mapping correctly, ensure you have Atlassian Access and both domains are claimed. it will be easier for you to change the user's email address from abc.com to xyz.com without any hassle and still have the users issues intact to avoid any duplicated account…

Hi @Sergey Nothing seems new as you can configure the notification scheme for fields only for "user custom field value" and "group custom field value". so a notification could be sent based on certain events. However, with the Issue updated event enabled, any field that gets updated should trigger a notification. To me it…

If I'm understanding this correctly, this could probably be an issue with the field configuration scheme. So on the field configuration, you've might have changed the description of the field based on a certain issue type hence that specific description shows. @Adam Dulberg open a new question about this and tag me with…

Hi @Adam Dulberg It is not possible for data to remain on the platform when it has been explicitly deleted, Jira Cloud is designed in such a way that once data is deleted, it's gone. Especially when it comes to custom fields, all these functions are done automatically. Is there a way for you to show or demonstrate this…

I'm not sure about that, probably worth asking Atlassian Customer Advocate on how that works.

Hi @Heather Russell you will need to search in Atlassian marketplace for an app which can do that. if none exist, you can design your own Cloud App to do that. Is there a particular use case to this requirement?

Hi @Harsha Gamage Welcome to Community! JSM provides 3 free agents and Jira provide max 10 users on free tier. these user count accumulates to the max number allowed. Therefore the reason you're facing this issue is most probably due to your Product Access for Jira Service Management being turned on, navigate to Site…

I believe to Integrate with Opsgenie properly you have to be on a paid plan on Opsgenie, if i'm not mistaken.

Hi @Jack Brickey I have a mixture of Premium and Standard Plans for Jira Software and Jira Service Management on separate instances. so it works for my Standard Jira Service Management Application.

Hi @John Funk Atlassian Access is based on Organization level, so the sandbox is actually added as an Application Product to your organization e.g. Jira Software or Jira Service Management, so the Atlassian Access Admin hub is not a separate entity with the sandbox instance. The same configuration in your Atlassian Access…

Hi @Darrel Jackson No, only include fields you want to update and not every field, what Jira does is update those fields once the import starts. Please always run a test in a Staging instance or test environment before applying to Production, in order to observe the behaviour of the action.

Hi @Darrel Jackson Welcome to Community! You can use the CSV importer feature from Jira Settings to achieve this. I would suggest, you identify all the issues that contains the source field data to know where they all exist then export those issues with that old field visible (as it will contain it's present data) and add…

Hi @Spatel Let me emphasize on the difference here. First of all, there's no API for adding users to group on Confluence Server. secondly, Atlassian Server Products doesn't use accountId, so the example you might be using is totally wrong. I would suggest you look into using an SQL query, if you want to add users to a…

Hi @Spatel There is no REST API to add users to groups on Confluence Server at least to my knowledge. However if you're Confluence Server, I believe you could easily do so with some SQL queries rather than write a whole script in powershell.

Hey @Luc Plas If that's the case then the process you're using on your Project is definitely wrong and you have to examine that first. As you need to structure your projects in a way that only members working on it has access and not everyone that's on the instance.

Hey @Nikhilesh Saggere Glad to help out, if the above answers your question. Please accept the answer, so other users can see it as a solution.

This "space,history,body.view,metadata.labels" you do not need to change as you're expanding the json. if you need a specific page, use CQL "rest/api/content/search?cql=space=TEST" mentioned on Advanced searching. 

Hi @Nikhilesh Saggere This is the URL https://confluence.sw.mycompany.com/rest/api/content you should use instead, since that url works. so your request should be curl -u user:password -X GET "https://confluence.sw.mycompany.com/rest/api/content?type=blogpost&start=0…

Hi @Nikhilesh Saggere Welcome to Community! If you're accessing via API endpoint from here https://developer.atlassian.com/server/confluence/confluence-rest-api-examples/ , the output should be in JSON and not HTML. However you should check the directory Confluence is installed, does yours say…

Thanks @Dave Meyer for the clarification and the open bug ticket, that's very helpful.

Hi @Anthony van Harten Welcome to Community! This is quite a pickle but there's always a solution. Looking at your description, you've fiddled with a couple of approaches. So here's a little idea on the problems you've mentioned. Firstly, on Jira, export is limited to 1K issues. Now the problem with that as you've noticed…

Hi @Dave Meyer Yes, I'm using the Org Admin API generated from here, and not the Personal API token from id.atlassian.com. Likewise API works if I'm using other endpoints, however this is the result I get when I use this endpoint to get Orgs {"data":[],"links":{"self":"https://api.atlassian.com/admin/v1/orgs"},"meta":null}…

Hi @sam saas The Docs mentioned "0 or more values of Org are returned" with that API. I don't particularly think the Org Id matters when creating the API. It just denotes where the API was generated. However I noticed that it returns an empty list instead with a 200 Status code. Which to me means that the API may not be…

Hey John, That's a good idea, Atlassian Support would be able to pick things up from there and let you know what's going on and provide a solution.

Hi @aokeeffe_guidewire_com Basically you can do that manually from the UI by changing the status to "Done" or "Closed" - depending on which status you have on your workflow. The question here is why complete the story first before any sub_task is done? As sub_task are broken task of a parent Issue. So, if you're going…