Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-557

Revision numbers when screens and workflows have been altered.

XMLWordPrintable

    • We collect Jira Service Desk 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 JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      Greetings,

      It is possible to have a revision number for screens and workflows in the event that they get altered? We ran into a scenario where a workflow (that was shared by multiple departments) was altered in a way that ended up breaking other group's workflows. The steps it took to recover everything were painful and long, a way to track and revert such alterations would really be helpful.

      Thank you,
      -rob

            [JSDSERVER-557] Revision numbers when screens and workflows have been altered.

            Alex Cooksey made changes -
            Resolution Original: Won't Do [ 10000 ] New: Low Engagement [ 10300 ]
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Charlie Marriott made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3011323 ] New: JAC Suggestion Workflow 3 [ 3646591 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2664048 ] New: JAC Suggestion Workflow [ 3011323 ]
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2323194 ] New: Confluence Workflow - Public Facing v4 [ 2664048 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 2051959 ] New: JSD Suggestion Workflow - TEMP [ 2323194 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2047354 ] New: JSD Suggestion Workflow [ 2051959 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 1279375 ] New: JSD Suggestion Workflow - TEMP [ 2047354 ]
            jonah (Inactive) made changes -
            Description Original: Greetings,

            It is possible to have a revision number for screens and workflows in the event that they get altered? We ran into a scenario where a workflow (that was shared by multiple departments) was altered in a way that ended up breaking other group's workflows. The steps it took to recover everything were painful and long, a way to track and revert such alterations would really be helpful.

            Thank you,
            -rob             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-557].
              {panel}

            Greetings,

            It is possible to have a revision number for screens and workflows in the event that they get altered? We ran into a scenario where a workflow (that was shared by multiple departments) was altered in a way that ended up breaking other group's workflows. The steps it took to recover everything were painful and long, a way to track and revert such alterations would really be helpful.

            Thank you,
            -rob
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-557 [ JSDCLOUD-557 ]

              Unassigned Unassigned
              196c0d95f696 rob m
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: