infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Bozarth (JIRA)" <>
Subject [jira] [Commented] (INFRA-14469) Create Livy JIRA project and import existing issues
Date Fri, 18 Aug 2017 18:58:00 GMT


Alex Bozarth commented on INFRA-14469:

Just finished going through the Open Livy JIRAs.

Things I did:
* Added a "Child-Issue" relation between JIRAs and their sub-task JIRAs
* Added relations and web links to the appropriate JIRAs
* Uploaded attachments to their appropriate JIRAs (since they weren't imported)
* Fixed a couple formatting issues (all happened to be on my own JIRAs)

Things I did not do:
* Go through any Resolved JIRAs (though I did add any relations between open JIRAs and resolved
* Add blocked by relations if all the blocker JIRAs were already resolved
* Update any descriptions or text (so any old href links are still there)

A couple notes:
* I used "Child-Issue" since converting to subtask was out of my abilities as a normal user.
* [~vanzin] we should probably lock the Cloudera Livy JIRA if it hasn't already
* I'll send out an dev email after this detailing what I did as well as linking to the new
JIRA for future use

> Create Livy JIRA project and import existing issues
> ---------------------------------------------------
>                 Key: INFRA-14469
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: JIRA
>            Reporter: Luciano Resende
>            Assignee: Gavin
>         Attachments: livy.json-3.log, livy.json-3-mapped, livy.json-3-mapped.log, livy.json.gz,
livy_users2.txt, livy_users.json, Screen Shot 2017-08-12 at 8.23.21 am.png, Screen Shot 2017-08-18
at 11.44.25 pm.png
> JIRA project name: LIVY
> I will provide an export of the existing JIRA issues and upload somewhere accessible.

This message was sent by Atlassian JIRA

View raw message