Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-11011

Improve documentation of 'Project Lead'

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.

      The current documentation says:

      Project Lead - user fulfilling the role of 'lead developer'. Used as the default assignee, and potentially elsewhere in JIRA.

      It's the phrase potentially elsewhere in JIRA that needs further explanation. What you need is an indicator that someone could specify "Project Lead" as part of a notification scheme, permission scheme, or security scheme instead of a particular user, allowing flexibility for a project administrator to change the project lead and have it automatically affect not only the default assignee, but also some permission or notification. Not sure how this fits into role based coming in 3.7, though.

            [JRASERVER-11011] Improve documentation of 'Project Lead'

            YJ Huang added a comment - - edited

            Every time a project lead is assigned to a project, she/he needs to be assigned as a project administrator to be able to configure the project and add members.

            That seems a redundant step.

            Why can't we set up the project lead as a role so that the project lead can be granted permission to administer the project?

            YJ Huang added a comment - - edited Every time a project lead is assigned to a project, she/he needs to be assigned as a project administrator to be able to configure the project and add members. That seems a redundant step. Why can't we set up the project lead as a role so that the project lead can be granted permission to administer the project?
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3047950 ] New: JAC Suggestion Workflow 3 [ 3680321 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2614382 ] New: JAC Suggestion Workflow [ 3047950 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2578337 ] New: Confluence Workflow - Public Facing v4 [ 2614382 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2357553 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2578337 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2124923 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2357553 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2087338 ] New: JIRA Bug Workflow w Kanban v6 [ 2124923 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 887168 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2087338 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 716453 ] New: JIRA Bug Workflow w Kanban v6 [ 887168 ]

              Unassigned Unassigned
              6e88f3fc96e7 Neal Applebaum
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: