Bugzilla – Full Text Bug Listing
| Summary: | provide rich editor for JIRA | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Mik Kersten <mik.kersten> | ||||
| Component: | Mylyn | Assignee: | Mik Kersten <mik.kersten> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | afalduto, brockj, ekuleshov, mik.kersten, yuri | ||||
| Version: | unspecified | Keywords: | helpwanted | ||||
| Target Milestone: | 0.9 | ||||||
| Hardware: | PC | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Mik Kersten
*** Bug 144621 has been marked as a duplicate of this bug. *** Mik, what is the plan about this issue? This is in 'helpwanted' limbo along with a few other important JIRA bugs. The problem is that I can't justify time on JIRA integration right now since I have to focus on the Tasks and Context APIs and UIs. Bugzilla, Trac, and the Generic web support have been working well as API drivers. Your and Brock's JIRA Connector contributions to date have been very helpful, but if we can not find a component lead wh oowns the quality of the JIRA support we may have to put it back into the Sandbox for 1.0 (at which point every connector should have a dedicated component lead). I would really like to avoid that and so I'm considering contacting Atlassian in order to see if they are interested in contributing. I actually thought that it would be possible to reuse common task editor, but if not, it is probably makes sense to remove current Jira editor, so users would be able to use web-based UI and query integration is working very well. The custom JIRA editor was providing very little value, had too many inconsistencies and has been removed from the latest dev build as suggested. Neither Rob nor I can currently dedicate much of 1.0 focus to JIRA, so a rich editor for JIRA based on the Tasks framework is staying in helpwanted land. Considering how small the TracTaskEditor subclass of AbstractRepositoryTaskEditor is, implementing one shouldn't be too difficult a task. We will have to ensure that the API allows an editor to be created without requiring offline support, although you mostly get the latter for free when you implement the attribute factory needed by the editor. *** Bug 162110 has been marked as a duplicate of this bug. *** Done. Html conversion and outline working too. Dev build will be available within an hour or two. Created attachment 53534 [details]
mylar/context/zip
|