Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-2166

Delete Contexts via Admin Screen

XMLWordPrintable

    • We collect Jira 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.

      If you are the user that created the context OR a user that is using a bad context, you can change it by:

      • go to chartboard
      • select an empty version (this was the only way i found to change the version that you look at in the taskboard, without getting a stack trace), delivery cycle 14 in this project.
      • after the chart loads, go to the taskboard
      • this will bring up the taskboard, but you will not get a stack trace because there are no tasks
      • change the context to a good context, or delete if you are the create user.

      Can this be a feature request that a jira administrator is able to delete contexts in greenhopper via some admin screen OR can the application catch the exception and show an empty task board with 'bad context' message to the user?

          Form Name

            [JSWSERVER-2166] Delete Contexts via Admin Screen

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3067106 ] New: JAC Suggestion Workflow 3 [ 3661492 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2622973 ] New: JAC Suggestion Workflow [ 3067106 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2322676 ] New: Confluence Workflow - Public Facing v4 [ 2622973 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2040691 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2322676 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2032601 ] New: JIRA PM Feature Request Workflow v2 [ 2040691 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 738502 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2032601 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Hoang Dong (Inactive) made changes -
            Component/s New: AgileBoard [ 14190 ]
            Component/s Original: ↓ Obsolete -- Context (Classic) [ 12974 ]
            Martin (Inactive) made changes -
            Backlog Order (Obsolete) Original: 1700000000
            Workflow Original: GreenHopper Kanban Workflow v2 [ 301901 ] New: JIRA PM Feature Request Workflow v2 [ 738502 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Minor [ 4 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Michael Tokar made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

              Unassigned Unassigned
              686bab2cfd9e Paul Hanneman
              Votes:
              5 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: