Opened 5 years ago

Last modified 5 years ago

#5062 new defect

table of tags of a changeset is incomplete

Reported by: aseerel4c26 Owned by: rails-dev@…
Priority: minor Milestone:
Component: website Version:
Keywords: changeset tags Cc:


Shows as "tags" only build, comment:2, created_by, version. The tag "comment" is missing. Although the listing apparently lists all changeset tags. This makes it not clear to newbies that the comment is also simply a tag.

Yes, the comment is the most important tag of a changeset, but this way it is not correct (data-wise).

Suggestion: Put the comment in the table of tags as first entry and link its key to the relevant wiki page (this is also missing). The key could be strong to be visible easier.

Another idea to keep the display correct?

It was correct before the UI change: example.

Change History (2)

comment:1 Changed 5 years ago by TomH

The comment is excluded because it's already shown at the top and there's no point showing it twice as it will just use screen real estate that could be used for other things.

Most users really shouldn't have to care about technical details like that fact that it is a "tag" on the changeset - it's just the description they enter when saving - so I don't see that this is a major problem, or indeed a problem at all.

comment:2 Changed 5 years ago by aseerel4c26

yes, I understand why it is not listed. But the description makes one think that the listed tags are all tags of the changeset.

"Most users" and "should not have to care" also means to make it harder for those who actually want to understand. This is also a problem for iD which also follows this concept of "should not have to care". For that reason some users think there is an area data type in the osm data and cannot understand that simply connecting a way's ends (and maybe some relevant tags) has the same effect. ;-)

"(Additional) tags" would be another option for the heading. Yes, or ignoring/accepting that in-correctness.

Last edited 5 years ago by aseerel4c26 (previous) (diff)
Note: See TracTickets for help on using tickets.