• We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      It would be nice if Atlassian could expose a way for plugin developers to add messaging to the Confluence Administration Console.

      Warnings, task reminders, or licensing reminders would be an example of the kinds of messaging that plugin authors would put in this section. Ideally, this could be separated by a heading for each plugin.

      Currently, one could use jQuery and a web-panel to perform this bit of trickery, but we run the risk of this breaking across versions and causing instability of the Administration Console.

            [CONFSERVER-23261] Administration Tasks Plugin Point

            I can confirm that on restarting Confluence, the task is removed from "Completed tasks" and reappears on the list. Steps to reproduce:

            1. Using the atlassian sdk, start the latest RC of Confluence and install this Gliffy SNAPSHOT: https://dl.dropbox.com/u/364573/gliffy-confluence-plugin-5.1-SNAPSHOT1.jar
            2. Navigate to the Admin task list
            3. Check off the Gliffy task
            4. Refresh the screen and notice that the task is moved to the "Completed tasks" area
            5. Restart the Confluence instance, and navigate back to the Admin task list

            Expected Results:

            • The task shows in the completed list

            Actual Results:

            • The task reappears in the task list (nothing shows in the completed list)

            I guess I don't understand what constitues an ignored task versus a completed task. Here's a rundown of the ideal requirements:

            • Allow the admin task to be checked off
              • Allow this value to persist across restarts
              • Record who checked off the task when (However, I'm not sure this is surfaced anywhere in the UI)
            • Allow the admin task to be reset by the plugin (Some condition causes the task to be recreated for review again)
              • Currently the granularity of the task is based on the show/no-show logic of the condition (but should pick up the previous checked value)

            Eric Chiang added a comment - I can confirm that on restarting Confluence, the task is removed from "Completed tasks" and reappears on the list. Steps to reproduce: Using the atlassian sdk, start the latest RC of Confluence and install this Gliffy SNAPSHOT: https://dl.dropbox.com/u/364573/gliffy-confluence-plugin-5.1-SNAPSHOT1.jar Navigate to the Admin task list Check off the Gliffy task Refresh the screen and notice that the task is moved to the "Completed tasks" area Restart the Confluence instance, and navigate back to the Admin task list Expected Results: The task shows in the completed list Actual Results: The task reappears in the task list (nothing shows in the completed list) I guess I don't understand what constitues an ignored task versus a completed task. Here's a rundown of the ideal requirements: Allow the admin task to be checked off Allow this value to persist across restarts Record who checked off the task when (However, I'm not sure this is surfaced anywhere in the UI) Allow the admin task to be reset by the plugin (Some condition causes the task to be recreated for review again) Currently the granularity of the task is based on the show/no-show logic of the condition (but should pick up the previous checked value)

            After a Confluence restart, the task should be in "Completed tasks" if the user has ticked it. If not, it's an issue - Can you confirm this is the bug you've observed?

            This seems way less functional than the AdminTask system which stores the state of ignoring a task and/or marking it as complete and by whom.

            The web-item stores the state of completing the task. I'm trying to understand your need: Do you need to make the difference between ignoring and completing? And is it important for you to know who has done it?

            AdrienA (Inactive) added a comment - After a Confluence restart, the task should be in "Completed tasks" if the user has ticked it. If not, it's an issue - Can you confirm this is the bug you've observed? This seems way less functional than the AdminTask system which stores the state of ignoring a task and/or marking it as complete and by whom. The web-item stores the state of completing the task. I'm trying to understand your need: Do you need to make the difference between ignoring and completing? And is it important for you to know who has done it?

            This is a little late, but it looks like we have no way of knowing if the user checked the checkbox to ignore the task in our condition. On restart of the instance, we would show the admin task once again, which shouldn't be the case. Right now, we're basing the condition on whether the user has visited our configuration page and storing this value in bandana.

            This seems way less functional than the AdminTask system which stores the state of ignoring a task and/or marking it as complete and by whom.

            Any thoughts on how we can improve this this late in the game?

            Eric Chiang added a comment - This is a little late, but it looks like we have no way of knowing if the user checked the checkbox to ignore the task in our condition. On restart of the instance, we would show the admin task once again, which shouldn't be the case. Right now, we're basing the condition on whether the user has visited our configuration page and storing this value in bandana. This seems way less functional than the AdminTask system which stores the state of ignoring a task and/or marking it as complete and by whom. Any thoughts on how we can improve this this late in the game?

            Looks good so far. If we have more feedback I'll leave a comment on this ticket.

            Eric Chiang added a comment - Looks good so far. If we have more feedback I'll leave a comment on this ticket.

            AdrienA (Inactive) added a comment - - edited

            The tutorial is available on DAC: https://developer.atlassian.com/display/CONFDEV/Creating+an+Admin+Task

            In short:

            • There is a web-item to display an admin task, with a title and description;
            • Plugins will be able to provide their WebItemCondition to tell whether the task should be shown.
            • Users will be able to tick them off.

            Eric, I know you don't have a version to test yet, but can you look at the screenshots and tell me whether it suits your need?

            AdrienA (Inactive) added a comment - - edited The tutorial is available on DAC: https://developer.atlassian.com/display/CONFDEV/Creating+an+Admin+Task In short: There is a web-item to display an admin task, with a title and description; Plugins will be able to provide their WebItemCondition to tell whether the task should be shown. Users will be able to tick them off. Eric, I know you don't have a version to test yet, but can you look at the screenshots and tell me whether it suits your need?

            We absolutely would love to have it in the 5.0 release. We've integrated anonymous usage statistics into our Gliffy v5.1 release that we're aligning with Confluence v5.0. So, two items initially:

            1. An action item for admins to check their opt-in status for anonymous usage statistics
            2. An action item for admins to check their license prior to expiration

            Eric Chiang added a comment - We absolutely would love to have it in the 5.0 release. We've integrated anonymous usage statistics into our Gliffy v5.1 release that we're aligning with Confluence v5.0. So, two items initially: An action item for admins to check their opt-in status for anonymous usage statistics An action item for admins to check their license prior to expiration

            Hey Eric,
            Do you think you will have time to make use of this plugin point before 5.0 shipps? Adrien is trying to get that in before our 5.0-BETA.

            Also, what were you planning to use it for? What task would you have?

            Sherif Mansour added a comment - Hey Eric, Do you think you will have time to make use of this plugin point before 5.0 shipps? Adrien is trying to get that in before our 5.0-BETA. Also, what were you planning to use it for? What task would you have?

            Fantastic! Let me know when you have an API we can work with.

            Eric Chiang added a comment - Fantastic! Let me know when you have an API we can work with.

            Hi Eric, I'm working on it, I hope to make it a feature of Confluence 5.0, but this is not a commitment.

            AdrienA (Inactive) added a comment - Hi Eric, I'm working on it, I hope to make it a feature of Confluence 5.0, but this is not a commitment.

            Thanks, Eric. I'd love to hear from other plugin partners as to how they would use this with some examples.

            For future reference: Plugin partners have more discussion on this feature request here: http://partners.atlassian.com/partner/Administration-Tasks-Plugin-Point.

            Sherif Mansour added a comment - Thanks, Eric. I'd love to hear from other plugin partners as to how they would use this with some examples. For future reference: Plugin partners have more discussion on this feature request here: http://partners.atlassian.com/partner/Administration-Tasks-Plugin-Point .

              aragot AdrienA (Inactive)
              e4741b7c6c16 Eric Chiang
              Votes:
              5 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: