Community
Participate
Working Groups
New bugzilla issue editor does not allow to save issue without submitting to server. Nothing happens when I use standard "Save" action and issue just disappear if I close editor and accept option to save isseue from a popup dialog.
*** Bug 159698 has been marked as a duplicate of this bug. ***
For 0.8 "save" needs to at least pop up a dialog that unsubmitted reports can not be saved. After that's done let's revisit to figure out whether we can support saving unsubmitted reports offline for 1.0.
Update: A warning dialog is now displayed if a save is attempted on the new bugzilla task editor.
Created attachment 52086 [details] mylar/context/zip
Any further improvement will happen post 1.0.
Rob: let's prioritize M2 things after we put M1 out, and use the 2.0 bucket for now.
*** Bug 176818 has been marked as a duplicate of this bug. ***
Deferring. This will require api changes and thorough ui design discussion.
*** Bug 199674 has been marked as a duplicate of this bug. ***
*** Bug 216568 has been marked as a duplicate of this bug. ***
Steffen: I think that you already have a good implementation strategy for this?
The basic idea is to create a local task for unsubmitted repository tasks. The task data for editing the repository task is stored in the offline storage location for that local task. That solves the problem that there is no unique handle as long as the repository task is unsubmitted. The offline storage will use the handle of the local task. The additional benefits of that approach is that the unsubmitted task shares all the properties of local tasks, i.e. task activation, contexts and scheduling. On submit the local task is converted to a repository task and the context etc. is copied to the new task. There are some details that need to be worked out. The unsubmitted tasks will propbably need special rules in the task list for visibility and grouping, e.g. always show up under a new "Unsubmitted" node. Also the editor factories need to recognize unsubmitted tasks and we need to decide if the context tab should be shown for those. A proto-type implementation is in JiraTaskEditor2.
Sounds perfect. In terms of UI, I think that it could work well enough if they were under a single Unsubmitted node as you suggest, and had a black outgoing arrow with a questino mark. Having a new UNSUBMITTED state or just reusing OUTGOING would make it easy for the guaranteed visibility rules to do the right thing.
Hmm. How those local tasks will deal with connector-specific task data and editor UI?
(In reply to comment #14) > Hmm. How those local tasks will deal with connector-specific task data and > editor UI? I don't see a problem since in unsubmitted form it is essentially a local task and once submitted becomes a repository task, editable via the appropriate connector editor.
Rob, I am just trying to understand the internals of how it is going to work. For example, one may need to edit an unsubmitted task several times before submitting and for that editing repository-specific editor need to be used. An unsubmitted task would need to have a proper connector type and repository url in order to be editable, so how that fits with the local tasks?
The connector editor factory will recognize local tasks with outgoing changes and the editor input will have the necessary information to retrieve task data. As I said in comment 12 there are some technical details that need to be addressed but the basics already work for editing JIRA tasks.
(In reply to comment #17) > ...there are some technical details that need to be addressed... Sorry about confusion. That is basically what I was asking.
This has been implemented as part of the task data API refactoring and works for Bugzilla and JIRA. The design is described in comment 12. Opened bug 234065 to address comment 13. Opened bug 235057 to address remaining problems.
