Skip to content

EPIC: tag items to categorise and organize #245

@iteles

Description

@iteles

As a person who believes that structure is key to organisation and trust in an app
I'd like to be able to tag my inputs with tags I make up myself
So that I can later have a better understanding of what is required from that capture at a glance and filter by the topics I am most interested in.

Tagging and projects are some of the features that I expect to most evolve as part of the app's user experience as they are the most critical but here is a starting point.

To be clear, I don't think that this will be useable as-is, but will certainly be a place to evolve from. We will have a much better UX for this within the next sprint but this is the starting point.

Acceptance Criteria

  • When I edit an existing item in my list of captures items,
    I see a text field where I can input tags
  • For stage 1, tags are input as a comma-separated list (a space required after each comma)
  • A submit button is clicked to save them
  • Each tag is checked against the saved tags (case-insensitive) and:
    • If a tag already exists, save the captures item against that tag
    • If a tag does not exist, create a new tag and save the captures item to it
    • Do not worry about leading and trailing spaces for now, this will not be the final UX MVP so we shouldn't waste time on fool-proofing for leading and trailing spaces yet - this version will only be used inside the dwyl team
  • Once tags are saved, take human back to the list of captures items
  • The list of tags should be displayed under the item.text
  • each tag should be a clickable hyperlink
    • clicking/tapping on the tag (hyperlink) should filter the items in the current list to just those with that tag.

Metadata

Metadata

Assignees

Labels

UIepicA feature idea that is large enough to require a sprint (5 days) or more and has smaller sub-issues.help wantedIf you can help make progress with this issue, please comment!needs-uiA feature idea that needs UI in order to be discussed/built.priority-1Highest priority issue. This is costing us money every minute that passes.questionA question needs to be answered before progress can be made on this issuetechnicalA technical issue that requires understanding of the code, infrastructure or dependencies

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions