Bugzilla – Full Text Bug Listing
| Summary: | add submission wizard to task editor | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Steffen Pingel <steffen.pingel> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | mik.kersten, robert.elves |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Steffen Pingel
I am not sure if this should be specific to JIRA. There is already more general bug report to eliminate duality of the task editor actions (submit vs. save). So, alternative approach could be to allow to directly edit all the fields (including resolution, assign to and all the custom ones). Steffen: could you put a point form summary of the workflows that need to be supported for JIRA? For Bugzilla we have this one, which is not currently supported: Change Product 1) Input required: Component value, Target Milestone value I'd like to have an overview view of the workflows that we know that we need to support, since there are quite a few different UI options for this. We also need to have an understanding of which workflows should be caputred client side and which need to be run server side. For example, the Bugzilla example above would be great to have done purely in the editor client side without the need for a separate dialog. But a server-side JIRA plug-in that imposes a precondition on submission might require delegating to the Web UI for a portion of that submission. As far as I know JIRA does not require additional user input when changing ticket state besides what the task editor already offers (although that might only apply to the standard workflow). When tickets are closed through the web interface JIRA will redirect to a page that allows to modify certain fields that are commonly edited but this is not required. I generally prefer Mylyn's current workflow where everything is editable in the editor and I would like to avoid adding modal dialogs (wizards) to the workflow when changing tickets. Even for attachments I find that inconvenient. To add to your list above: Bugzilla: Resolve Ticket 1) Input required: Comment JIRA has a few operations that are currently not supported by Mylyn some of which require input: Clone: Summary Link: Link type, Linked issue Move: Project, Issue type, Custom fields etc. Vote: Watch: Log work: Time spent, Comment (In reply to comment #2) > Change Product > 1) Input required: Component value, Target Milestone value By the way, shouldn't this simply update content of linked Component and Target Milestone dropdowns and allow user to select them, so Mylyn would do the proper submission (2 step if needed) under the hood. (In reply to comment #4) > By the way, shouldn't this simply update content of linked Component and Target > Milestone dropdowns and allow user to select them, so Mylyn would do the proper > submission (2 step if needed) under the hood. Yes, we could look investigate the possibility of updating the viable attributes and refreshing the editor upon product selection. Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |