General improvements to Task report and Action item macros

XMLWordPrintable

    • 1

      Issue Summary

      • Some behavior and look and feel of the Tasks/Action items can be confusing to new users.

      Current behavior

      1. Task and Action items are used interchangeably in Confluence, and when new users try to add a task, they'll need to know that they have to use the "Action item" macro.
        • And when we want to display all of these "action items", users will have to know that they'll need to use the "Task report" macro.
      2. The "Task report" macro also has a heading by default, called "Task report", but the heading disappears if tasks are present, and shows up again when there's no tasks.
        • If the "Looking good, no incomplete tasks." message is not present when there are no tasks present, this would be fine, but this message is already present when viewing the page/macro with no tasks.

      Suggested behavior

      1. For the "Action items" macro
        • Use a consistent naming scheme for "Tasks" and/or "Action items"
        • As most other parts of Confluence use "Tasks", it would be good to rename "Action items" to "Tasks", or something similar.
        • Note: As most users familiar with Confluence use the "[" and "]" shortcut to add tasks, this might not be something they've noticed, but new users would definitely benefit the consistent wording.
      2. For the title/heading in the "Tasks report" macro.
        • Either consistently show the heading, or hide it entirely.
        • Having the option to show/hide headings in the macro configuration would good too.
        • Note: As a workaround, we could add a heading manually, but this causes there to be duplicate headings when there are no tasks present.

            Assignee:
            Shubh Trivedi
            Reporter:
            Sattesh M
            Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: