• 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

            This issue will not be addressed as it is related to Classic boards, which are no longer being improved and will be removed in the future. We encourage you to migrate to the new Agile boards for all future work.
            Regards,
            GreenHopper Team

            Michael Tokar added a comment - This issue will not be addressed as it is related to Classic boards, which are no longer being improved and will be removed in the future. We encourage you to migrate to the new Agile boards for all future work. Regards, GreenHopper Team

            Jeremy Largman added a comment - See also https://answers.atlassian.com/questions/28829/how-to-edit-or-delete-shared-greenhopper-contexts-by-users-who-are-no-longer-around , a related request.

            Paul Hanneman added a comment - - edited

            This issue was derived from GHS-814 in the support.atlassian.com jira

            Paul Hanneman added a comment - - edited This issue was derived from GHS-814 in the support.atlassian.com jira

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

                Created:
                Updated:
                Resolved: