Prince Nyeche - ELFAPP Atlassian Partner

Hey @Dmytro Rudenko _ Release Management Yes, I believe there will be a wave of apps that temporarily disappear as a result of this deprecation. The Atlassian Marketplace for Cloud is increasingly being populated by former Data Center vendors moving into Cloud, and I think vendors who cannot adapt to Forge, or at least…

@Founder - NewSysRS Indeed, anyway to reduce the maintenance time on Forge is always half the battle won.

@Founder - NewSysRS For your use case, I recommend enforcing strict limits on imported files. For example, define a fixed maximum file size such as 2MB or 5MB and restrict uploads to specific attachment extensions. Avoid leaving file uploads open-ended for users. This validation should start at the frontend, where you…

@Josh Thanks. 

@Arkadiusz Wroblewski Exactly, that’s precisely the point. No two migrations are ever the same. In fact, there are cases where running the same migration dataset multiple times can produce different outcomes. What ultimately leads to a successful migration is the process of continuous iteration, validation, and…

@Caterina Curti - Thanks for stopping by. That may absolutely be possible, but the underlying limitations still exist. The point of this article isn’t to dismiss one approach over the other. It’s to highlight both options clearly so developers can make informed architectural decisions early. Good developers don’t just ask,…

Hey @Yatish Madhav Thanks for sharing. At its core, programming concepts remain the same across languages. PHP, as you know, is largely functional in style, and many of those principles translate well to Forge, which runs on Node.js (JavaScript). That said, it is a different language, so there’s naturally a learning curve.…

@James Rickards _SN_ I think you've probably misread this article. I never stated in my article that the REST API is being deprecated. I made two clear and factual points: Atlassian is encouraging vendors to move from Connect to Forge. For organizations prioritizing stronger security and long-term alignment with the…

@James Rickards _SN_ Forge is the new power house for everything apps related. Older APIs will be gone to make way for the newer technologies which will be embedded into the Atlassian API framework where applicable. In regards, to the backup API, yes that is deprecated as well and won't work. Atlassian have newer backup…

Hey @Bernice Dickens Are you using this jiraone library to extract your Jira work items or are you using something else?

That gets the users from the organization's managed directory. Jira's directory is local to the Jira site; there's another endpoint for that, which you can use to get all users within a Jira site rather than all managed users within an organization.

Hey @Jackson Kelley You can look in my Python library to see how this is implemented or use it to get the information you want.

Hi @Christa Meck The document mentions to use <cloudId> and not the <OrgId> I believe that's why you're getting the 404 error because the resource doesn't exist. This document shows how you can retrieve your site cloud ID

Hi @Roy Hillel I believe if you've connected your repository to Jira, you should be referring to the workspace itself as the container. You can look into the security workspace id for that info.

Hey @Thomas Stanek There's none at the moment as I haven't had the time to work on it but by next month, hopefully, will provide a fix to it. I'm tracking the problem here for reference.

Hey @Reinaldo This seems like a network/proxy/firewall problem rather than the library not being available. You can try pip install jiraone==0.8.5 Which is a specific version. 

Have you read this article? It explains how to do it via API with a few lines of Python code.

Hey @Rodolfo Arriesgado So You can add these arguments, errors, and encoding to the issue_export function, and the function will use those when writing the output into a CSV file. However, the script will automatically use the default encoding and replace it if a character can't be decoded within the script. You…

Hey @Henry Santos This should be an easy problem to fix. Typically, you can get the current visibility of each ticket and update the comment with that visibility. Each ticket has a key via API as "jsdPublic": true Unfortunately, CSV options don't add the visibility part for comments according to this feature…

I believe this is one of those rare instances where a session might have been lost during transit when querying Jira issue via the API. I'm not sure what the cause is, but if, you receive this for a small fraction of the tickets. Probably what you can do is auth again within that loop using the same variable name you used…

I believe you've figured out a way to do this in a loop. If you're not scripting a solution, the API call might not be as intuitive as required. However, why struggle with API when there are free apps that perform bulk creation of organization available on the Atlassian Marketplace?

Yes, the solution is still viable for deleting Jira or JSM customers.

It seems you're splitting the result in half because you get more data in maxResult compared to your browser. Your code uses maxResult 200, try using 100 as batchsize and see if you get the same result with the browser.

I'm not entirely sure why that happens for your environment but I suggest using the next best alternative which is the field_type argument that would give you exactly the export you need if the include_fields argument keeps throwing an error about the "Key" field not being available.

Hey @Birgit Saalfeld There's no difference between the method export_issues and issue_export as both reference the same object. However, when dealing with fields argument, the names of the fields are case-sensitive and have to be represented the way they appear on Jira. For example, if you're looking for these fields…

Hey @Yatish Madhav The webhook.site does work with a simple connection, not sure how you've configured it though if it's not working for you. To your question, this article was more than 3 years ago. So the list of supported events has increased since then, you can find the updated list here. For authentication using the…

Hi, What datatype is code? Shouldn't that be { ... code: code, ... } Since you're passing an object to the request.

I believe those warnings are from the notebook API being used. Probably there's a configuration within the application settings to turn warnings off but I'm unsure about that.

Hey @jaych if you are connected to any storage plugin within MS Fabric such as onelake, you can add a directory path or URI by using the folder argument and set a file name by using the final_file argument (optional). For example issue_export(folder="<storage_path_URI_here>", final_file="<file_name>") The concept here is…

Hey folks, the latest version of jiraone comes with an asynchronous function to extract the issue history very fast. Example # import statementPROJECT.async_change_log( jql, folder="TEST", file="sample.csv", workers=20, flush=10 ) An explanation of the arguments can be found here