Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #7988 (closed)

Opened 8 years ago

Closed 7 years ago

RFE: Tag selection workflow

Reported by: saloynton Owned by: saloynton
Priority: minor Milestone: Usability Backlog
Component: General Version: n.a.
Keywords: n.a. Cc: wmoore, dgaudioso
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

The option in the tag selection is without the list of selected tag, and given the work outlined in #6019 the necessary workflow for the tag selection can be made and the appropriate mock-ups made.

Attachments (1)

tag selection dialogue.pdf (132.0 KB) - added by saloynton 7 years ago.

Download all attachments as: .zip

Change History (14)

comment:1 Changed 7 years ago by saloynton

  • Status changed from new to accepted

Changed 7 years ago by saloynton

comment:2 Changed 7 years ago by saloynton

  • Cc dgaudioso added
  • Remaining Time set to 0.2

comment:3 Changed 7 years ago by saloynton

  • Owner saloynton deleted
  • Status changed from accepted to new

comment:4 Changed 7 years ago by saloynton

To discuss the possible options with Dom (pdf attached), with an awareness to both the short term implications for the development and longer term evolution of tagging.

comment:5 Changed 7 years ago by wmoore

Have a look at http://harvesthq.github.com/chosen/ (multiple select). This is an easy way to improve our existing multi-select.

comment:6 Changed 7 years ago by jburel

  • Sprint changed from 2012-02-14 (8) to 2012-02-28 (9)

Moved from sprint 2012-02-14 (8)

comment:7 Changed 7 years ago by jburel

  • Sprint changed from 2012-02-28 (9) to 2012-03-13 (10)

Moved from sprint 2012-02-28 (9)

comment:8 Changed 7 years ago by saloynton

  • Summary changed from Bug: Tag workflow to RFE: Tag selection workflow

comment:9 Changed 7 years ago by saloynton

Will: Is the implementation of this via the 'Chosen' JavaScript? plugin realistic to be implemented for this release?

comment:10 Changed 7 years ago by wmoore

Afraid not, unless Dom has time to look at it? He may have other ideas too?

comment:11 Changed 7 years ago by saloynton

Moving into the usability backlog, it can be moved back into 4.4 milestone if the defined set of changes look to incorporate any tag changes.

comment:12 Changed 7 years ago by saloynton

  • Milestone changed from OMERO-Beta4.4 to Usability Backlog
  • Owner set to saloynton
  • Remaining Time 0.2 deleted
  • Sprint 2012-03-13 (10) deleted

comment:13 Changed 7 years ago by saloynton

  • Resolution set to fixed
  • Status changed from new to closed

Closing moved to usability backlog on gdoc.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.84468 sec.)

We're Hiring!