Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-47876

labels in CQ version of AAC largely useless because of cruft

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      Labels are essential for "helpers" such as plugin vendors to monitor for questions on their plugins.

      The label selection dialog is largely useless as it stands because of all the cruft (see screenshot). Lots of people don't even know how to use labels, they just paste their question there, hence cruft.

      The label suggestions should be sorted by popularity... this would cause natural clumping around one or two labels, rather than a distribution of between many. Perhaps even show the number of these labels in parens.

      This distribution makes it impossible for me to watch all possible labels.

      Not only that, the list is actually truncated with no indication that it's truncated. This makes it impossible for a user to find the correct label for my plugin, eg addon-com.onresolve.jira.groovy.groovyrunner.

        1. Bildschirmfoto 2014-10-15 um 00.14.37.png
          Bildschirmfoto 2014-10-15 um 00.14.37.png
          64 kB
        2. new-topic-selector.png
          new-topic-selector.png
          55 kB
        3. screenshot-1.png
          screenshot-1.png
          27 kB

            [CONFSERVER-47876] labels in CQ version of AAC largely useless because of cruft

            I do not agree with the reason for sorting by popularity without a natural sort order as well. If am looking for a label, I would think of words and I want to look them up. When I start typing is starts bringing up words but then I need to erase the whole word and start over again. A very tedious process. Our eyes scan things quicker than people typing in words.

            Norman Abramovitz added a comment - I do not agree with the reason for sorting by popularity without a natural sort order as well. If am looking for a label, I would think of words and I want to look them up. When I start typing is starts bringing up words but then I need to erase the whole word and start over again. A very tedious process. Our eyes scan things quicker than people typing in words.

            We will sort matching topics by popularity (cf. new-topic-selector.png screenshot) and the list load results until they are all shown.

            Regarding "noobs" creating topics, it's a good idea, I've created an issue https://jira.atlassian.com/browse/CQ-1509

            Julien Michel Hoarau (Inactive) added a comment - - edited We will sort matching topics by popularity (cf. new-topic-selector.png screenshot) and the list load results until they are all shown. Regarding "noobs" creating topics, it's a good idea, I've created an issue https://jira.atlassian.com/browse/CQ-1509

            JamieA added a comment -

            I'd also prevent low-karma noobs from creating labels, definitely agree about marketplace lookup. Maybe a wizard... which product? Does this refer to a plugin? If yes - which plugin?

            Anyway, this issue appears to be code-complete, I would love to know in what way it was solved. With Julien's background in gamification it could be an interesting solution.

            JamieA added a comment - I'd also prevent low-karma noobs from creating labels, definitely agree about marketplace lookup. Maybe a wizard... which product? Does this refer to a plugin? If yes - which plugin? Anyway, this issue appears to be code-complete, I would love to know in what way it was solved. With Julien's background in gamification it could be an interesting solution.

            i agree, most of the users who request help via Atlassian Answers go there directly and dont care about labels all along, imho only a handful get there from the marketplace plugin page. So the labeling within the answers system should work quite comfortably which it doesn't.

            Moderators would maybe help? I cant tell if Atlassian support stuff stick there around. Imho they dont label questions asked to the product the question belongs to (at least if its not a core product). So sometimes questions either dont get answered or dont get answered in the best way (As the product maintainers did not get notified due to missing tags/labels).

            To come back to the actual issue here, would it be a possible improvement to have some kind of marketplace lookup (at least if the label starts with addon...) ?

            And when the question is asked the actual lookup within the question doesnt work at all, does it? see the Bildschirmfoto 2014-10-15 um 00.14.37.png

            Frank Stiller added a comment - i agree, most of the users who request help via Atlassian Answers go there directly and dont care about labels all along, imho only a handful get there from the marketplace plugin page. So the labeling within the answers system should work quite comfortably which it doesn't. Moderators would maybe help? I cant tell if Atlassian support stuff stick there around. Imho they dont label questions asked to the product the question belongs to (at least if its not a core product). So sometimes questions either dont get answered or dont get answered in the best way (As the product maintainers did not get notified due to missing tags/labels). To come back to the actual issue here, would it be a possible improvement to have some kind of marketplace lookup (at least if the label starts with addon...) ? And when the question is asked the actual lookup within the question doesnt work at all, does it? see the Bildschirmfoto 2014-10-15 um 00.14.37.png

            JamieA added a comment -

            relates to CQ-798, but not the same as.

            JamieA added a comment - relates to CQ-798 , but not the same as.

              jhoarau Julien Michel Hoarau (Inactive)
              714061b26763 JamieA
              Affected customers:
              1 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: