Download 50000 Issues from JIRA cloud into JSON file
- or -
Post a project like this£250(approx. $314)
- Posted:
- Proposals: 9
- Remote
- #2276778
- OPPORTUNITY
- Expired
AI & Data Science Engineer | Nodejs | Ruby On Rails | AWS | GCP | Python | React | Angular |
Auckland
Customized Mobile apps | Website Design & Development | Digital Marketing |E-commerce Solutions
Ahmedabad
Experienced Graphics designer |Experienced WordPress Full Stack|SharePoint Expert|Data Entry Team |flyer/business card/Brochure||2DAnimation||Photoshop work|
Islamabad
2552841101190879962108868116016092062434227239423598252370555
Description
Experience Level: Expert
Estimated project duration: 1 - 2 weeks
I need to develop a python routine to use the JIRA REST API to download issues from a specified project into a JSON file. No UI is required. the JIRA Cloud URL, id, credentials and project can be set-up in variables.
The routine needs to:
* Create a new JSON file using date-time of creation for uniqueness in current folder. Internal structure and field names can mimic that found in JIRA.
* For each issue found - create a JSON structure using the issue key as the internal unique identifier
* Allow standard and custom fields to be specified in the routine explicitly - not pull every field into the JSON structure
* Interpret issues and pull down the list of sub-issue into a sub-issue (id and linktype) substructure within the issue structure
* Interpret EPIC issues and pull down the list of EPIC-linked issues into a sub-issue (id and linktype=EPIC-link) substructure within the issue structure
* Establish proxy issues for issues from outside the specified project that are linked to issues in the specified project.
* Establish proxy "component" issues for components linked to issues in the specified project.
The routine needs to:
* Create a new JSON file using date-time of creation for uniqueness in current folder. Internal structure and field names can mimic that found in JIRA.
* For each issue found - create a JSON structure using the issue key as the internal unique identifier
* Allow standard and custom fields to be specified in the routine explicitly - not pull every field into the JSON structure
* Interpret issues and pull down the list of sub-issue into a sub-issue (id and linktype) substructure within the issue structure
* Interpret EPIC issues and pull down the list of EPIC-linked issues into a sub-issue (id and linktype=EPIC-link) substructure within the issue structure
* Establish proxy issues for issues from outside the specified project that are linked to issues in the specified project.
* Establish proxy "component" issues for components linked to issues in the specified project.
Bart N.
100% (10)Projects Completed
15
Freelancers worked with
14
Projects awarded
59%
Last project
5 Feb 2019
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies