Prince Nyeche - ELFAPP Atlassian Partner

Hi @ayush.kholiya I believe collecting the URL of the instance can be considered personal data(if I'm not mistaken). However, if you're taking personally identifiable data then you have to provide a means whereby the user can be informed that you're collecting that data or provide a means where they can have it…

Hi @gtrig Yes, it is possible. On the cloud, you can always install an app as a "private app" and this way you can be able to use a custom app specifically for your instance. See more on the documentation

Hi @Rob Horan You could use a free app to do import of users and add users to groups, since you have the CSV file of the data, check out this app. If I'm not mistaken the sandbox has a feature which can copy production data. I believe you have to spin up the sandbox environment after those data has been imported into…

Hi @Angel Todorov I think a more robust way to go about summing up story point across different hierarchies is using ScriptRunner addon.

Hi @[deleted] The image I showed is a project I've had since 2019 and such feature is available for it now (scrum or kanban). So I'm not sure why you say "this feature is not active". Given that they are software projects and you have access to the board configuration, you can enable it. If they are not software projects…

Hey @Anumalla Nithinraj Using REST API is the best option. I wrote this article a while back on how to extract entire issue history into a CSV file using python.

Since the source setting configuration is correct. I'm assuming that your filters there are pulling out all issue types and not a specific set of issue type?

Hi @[deleted] The roadmap feature is available on company-managed project if that's what you're asking, you can see that from your board settings to enable it.

If you're on a standard cloud plan, you might want to seek proper help from support, so they can look into the files you're trying to import and explain better. On community you can't share such sensitive information.

What error are you getting for attachments? Typically if it's the same instance, the images can be imported into the project. However if it's from a different instance, there's a workaround to import attachments.

Hey @Cecilia Tufvesson Prior to import you can change the format of the datetime to the format you want before import from the CSV importer page. It is imperative that you get the right format as saved on the CSV file to avoid any potential errors. Please do not change the Advanced configuration for datetime, that would be…

Hi @Peter Yoon Please could you clarify your question on "missing epic", what do you mean by that? Is the epic issue type not available on your Advanced Roadmap?

I believe you need to pay for it to be able to perform changes. Probably back then it might have been on trial.

Your project is a team-managed project, so you don't have multiple screens. Epic Link works differently on such project, you will need to add the issue to a Parent after creation by visiting the issue and click on add epic.

That doesn't look like an official API for Jira software! Then this is an expected behavior because it can stop working at anytime without any notice.

If it's not listed here then its not an official API.

You should go to your project settings > screens and add that field instead.

Getting such results, I don't think you have access to such content and also this might be a permission problem.

Good, now can you try to access that endpoint you want on the browser and see if you get a response. You might want to open up your developer console (Network tab) to see the response you get.

Hi @Maria Brobonea Is the instance accessible from your browser and are you able to login normally from there?

@[deleted] You should ask your admin if they can add you into those other projects (permission scheme) so you can manage the sprints. You do not need to upgrade your Jira privilege on the instance to manage sprint. You just need the right permissions on the projects you want to manage. I believe your admin should start…

From a search, you will need to search individual issues to get probably the sprint id to know which board the issue is then you can get the board with the board API. How it is a lengthy process just keep that in mind as multiple apis needs to be used.

If you're not using ScriptRunner addon then you have to use REST API provided by Atlassian. Even ScriptRunner uses that behind the scene, so connecting to a third party system will definitely need you to use the API provided. Although there are various methods to connect to the same API resource which are documented here

That's great to hear @Teja .The simpler the better.

Great to hear that @Teja Please accept the answer if the solution answers your question. So other users can use a similar solution.

Hi Based on the document for successful connection, you have to input your email address and API token of your user for your JSM cloud instance. Did you do that? If yes, ensure that the project key you're trying to fetch data from is correct and is in capital letters.

No, you have to do the other configurations manually. I would suggest going through the link I sent. Exporting the issues are done from the issue navigator page. It would be good as well, if you read articles that explains how migrating projects from one instance to another work. You might be having an expectation of the…

# previous import statement import json user = "username"password = "password"link = "https://yourinstance.jira.com" LOGIN.api = FalseLOGIN(user=user, password=password, url=link) jql = "project = 'xyz' and issuetype = Epic and status not in (Closed) and Testers in (tnaik)" count = 0 while True: load =…

Okay! That's the payload you need. Now just do the append as before and ensure you add the import from jira-python so you can update the issue (if using that route). otherwise another method you could use to update the issue is # previous statements # ... value.append({"name": "tnaik1"}) # payload to post to edit issue…

from jiraone import LOGIN, endpoint, fielduser = "username"password = "password"link = "https://yourinstance.jira.com" LOGIN.api = FalseLOGIN(user=user, password=password, url=link) keys = "GTN-32231" name = "Testers" # get field issues = LOGIN.get(endpoint.issues(keys)).json() fields =…