• Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • None
    • 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 to have a label-removal macro to ensure that certain labels are automatically removed if created.

            [CONFSERVER-9510] remove-label macro?

            BillA added a comment -

            Thank you for raising this issue. While we can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now.

            Thanks again for your idea.

            Bill Arconati,
            Confluence Group Product Manager

            BillA added a comment - Thank you for raising this issue. While we can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Thanks again for your idea. Bill Arconati, Confluence Group Product Manager

            We have a similar use case as Don. We use Scaffolding and Ad Hoc Workflows to route certain "forms" through a workflow process. Depending on what a user selects in the scaffold (e.g. "Urgent" or "Non-urgent"), the form needs to take a different fork in the workflow. It will be handled by different people, trigger different notifications, etc.

            If the scaffold is ever updated (e.g. it was originally "Non-Urgent" but gets changed to "Urgent"), we need to:
            1) add the new corresponding labels (using add-label macro, which works great), and
            2) clear out the old labels (need a remove-label macro).

            Perhaps users could remove specified labels or all labels, such as:

            {remove-label:labelname1,label-name2,labelname3} {remove-label:@all}

            Alison Reid added a comment - We have a similar use case as Don. We use Scaffolding and Ad Hoc Workflows to route certain "forms" through a workflow process. Depending on what a user selects in the scaffold (e.g. "Urgent" or "Non-urgent"), the form needs to take a different fork in the workflow. It will be handled by different people, trigger different notifications, etc. If the scaffold is ever updated (e.g. it was originally "Non-Urgent" but gets changed to "Urgent"), we need to: 1) add the new corresponding labels (using add-label macro, which works great), and 2) clear out the old labels (need a remove-label macro). Perhaps users could remove specified labels or all labels, such as: {remove-label:labelname1,label-name2,labelname3} {remove-label:@all}

            baem le added a comment -

            hi, the issue is open since 2007. are there any activities about this idea?

            we are very interested in such a macro to remove all labels from a page.

            greets

            baem le

            baem le added a comment - hi, the issue is open since 2007. are there any activities about this idea? we are very interested in such a macro to remove all labels from a page. greets baem le

            Don Gamble added a comment -

            We would also like to see this functionality.

            In our case we are using the

            {rate} macro to allow users to rate page content and the Reporting plugin to report on the quality of all pages in a space.

            The {rate}

            macro is included as part of each page by a standard user macro that we use on every page containing content . In addition to content pages we have the concept of home pages and directory pages. These are also built with standardized user macros. The report generated by the Reporting plugin reports on the rate of every page. To avoid reporting on non content pages (i.e. home and directory pages) the report was enhanced to exclude pages that have a label of "dont-rate".

            Current we use the

            {add-label:dont-report}

            within our home and directory user macros to ensure that home and directory pages are excluded from the report. But, we also would like to use a

            {remove-label:dont-report}

            in our user macro for content pages to ensure that content pages can't be excluded from reporting.

            Don Gamble added a comment - We would also like to see this functionality. In our case we are using the {rate} macro to allow users to rate page content and the Reporting plugin to report on the quality of all pages in a space. The {rate} macro is included as part of each page by a standard user macro that we use on every page containing content . In addition to content pages we have the concept of home pages and directory pages. These are also built with standardized user macros. The report generated by the Reporting plugin reports on the rate of every page. To avoid reporting on non content pages (i.e. home and directory pages) the report was enhanced to exclude pages that have a label of "dont-rate". Current we use the {add-label:dont-report} within our home and directory user macros to ensure that home and directory pages are excluded from the report. But, we also would like to use a {remove-label:dont-report} in our user macro for content pages to ensure that content pages can't be excluded from reporting.

            My personal use for the macro is in the "Replace-and-Render" plugin. I'm using it to automatically insert tags into projects based on controls displayed via the "Scaffold" plugin. Unfortunately, editing the value of the controls leaves the old tags. As such, forcing a removal would then allow for us to keep tags automatically inserted and updated.

            I was thinking it could also be useful as active prevention of certain tags - like in a project wiki, preventing tags like "project", "work", "info" - anything generic or insufficiently descriptive.

            http://confluence.atlassian.com/display/CONFEXT/Replace+and+Render+Plugin

            Christopher nies added a comment - My personal use for the macro is in the "Replace-and-Render" plugin. I'm using it to automatically insert tags into projects based on controls displayed via the "Scaffold" plugin. Unfortunately, editing the value of the controls leaves the old tags. As such, forcing a removal would then allow for us to keep tags automatically inserted and updated. I was thinking it could also be useful as active prevention of certain tags - like in a project wiki, preventing tags like "project", "work", "info" - anything generic or insufficiently descriptive. http://confluence.atlassian.com/display/CONFEXT/Replace+and+Render+Plugin

            Thanks for the suggestion, Christopher. What would you use this for?

            Matt Ryall added a comment - Thanks for the suggestion, Christopher. What would you use this for?

              Unassigned Unassigned
              2e9fd7efa144 Christopher nies
              Votes:
              9 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: