#4 — Assigning owners, importance to issues is too cumbersome
by
Martin Aspeli
—
last modified
Jun 20, 2012 01:21 AM
| State | Resolved |
|---|---|
| Version: | |
| Area | User interface |
| Issue type | Feature |
| Severity | Medium |
| Submitted by | Martin Aspeli |
| Submitted on | Dec 12, 2005 |
| Responsible | Martin Aspeli |
| Target release: |
—
|
Would like to use "Add response" screen for this the same way we assign workflow states
Added by
Martin Aspeli
on
Dec 19, 2005 12:09 AM
Further, we should generalise the 'issue state before/after' functionality into a list of changes performed by a response. The response could hold a list of dicts, each with keys 'name', 'before' and 'after', and the UI could output: changed [name]: [before] -> [after].
Added by
Martin Aspeli
on
Dec 19, 2005 01:39 AM
I'm working on this, but it's a pain because it requires migration. Stay tuned. :)
Issue state:
open
→
in-progress
Added by
Martin Aspeli
on
Dec 20, 2005 01:42 AM
This is now fixed in svn.
Issue state:
in-progress
→
resolved
Added by
kuaile
on
Jun 20, 2012 01:21 AM
http://www.michaelkorsmkvip[…]chael-kors-satchel-c-8.htmlhttp://www.michaelkorsmkvip[…]ors-messenger-bags-c-5.html
http://www.michaelkorsmkvip[…]ael-kors-kingsbury-c-4.html
http://www.michaelkorsmkvip[…]-kors-jet-set-tote-c-3.html
http://www.michaelkorsmkvip[…]-hamilton-handbags-c-2.html
http://www.michaelkorsmkvip[…]-kors-classic-tote-c-1.html
No responses can be added.
If you can, please log in before submitting a reaction.