Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-88391

Issues being scheduled for a wrong person in Portfolio Plan

XMLWordPrintable

      There is a scheduling bug which results in issues being scheduled for a wrong person and surfaces under the following circumstances:

      • It concerns only sub-tasks having either an assignee in Portfolio or Jira assignees with a Jira assignee level above or equal sub-tasks.
      • There must be a certain number of possible member/sub-task assignments (which resource can be assigned to which sub-task).

      Workaround:
      Try reducing the possible assignments of sub-tasks. That means that if each of sub-tasks has either an assignee in Jira or an assignee in Portfolio, the problem will not appear.

            [JRACLOUD-88391] Issues being scheduled for a wrong person in Portfolio Plan

            Kate Durnell made changes -
            Component/s Original: Plan (Advanced Roadmaps) - Roadmap [ 61013 ]
            Component/s New: Plans - Timeline [ 77924 ]
            Key Original: JSWCLOUD-19307 New: JRACLOUD-88391
            Project Original: Jira Cloud [ 18511 ] New: Jira Platform Cloud [ 18514 ]
            Dylan made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Long Term Backlog [ 12073 ] New: Closed [ 6 ]
            Dylan made changes -
            Labels New: stale-bulk-close202006
            Owen made changes -
            Component/s New: Advanced Roadmaps [ 61013 ]
            Component/s Original: Advanced Roadmaps [ 61212 ]
            Key Original: JPOCLOUD-2071 New: JSWCLOUD-19307
            Project Original: Portfolio for JIRA Cloud [ 18510 ] New: Jira Software Cloud [ 18511 ]
            Owen made changes -
            Component/s New: Advanced Roadmaps [ 61212 ]
            Component/s Original: Scheduling [ 46297 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 2679709 ] New: JAC Bug Workflow v3 [ 3439820 ]
            Status Original: Verified [ 10005 ] New: Long Term Backlog [ 12073 ]
            Albert Kavelar made changes -
            Status Original: Open [ 1 ] New: Verified [ 10005 ]
            Paulo F. (Inactive) made changes -
            Summary Original: Issues being scheduled for a wrong person in Plan New: Issues being scheduled for a wrong person in Portfolio Plan
            Paulo F. (Inactive) made changes -
            Description Original: There is a scheduling bug which results in issues being scheduled for a wrong person and surfaces under the following circumstances:

            * It concerns only sub-tasks having either an assignee in Portfolio or Jira assignees with a Jira assignee level above or equal sub-tasks.
            * There must be a certain number of possible member/sub-task assignments (which resource can be assigned to which sub-task).

            Workaround:
            To work around the problem we try to reducing the possible assignments of sub-tasks. That means that if each of sub-tasks has either an assignee in Jira or an assignee in Portfolio, the problem will not appear.             		New: There is a scheduling bug which results in issues being scheduled for a wrong person and surfaces under the following circumstances:

            * It concerns only sub-tasks having either an assignee in Portfolio or Jira assignees with a Jira assignee level above or equal sub-tasks.
            * There must be a certain number of possible member/sub-task assignments (which resource can be assigned to which sub-task).

            Workaround:
            Try reducing the possible assignments of sub-tasks. That means that if each of sub-tasks has either an assignee in Jira or an assignee in Portfolio, the problem will not appear.
            Paulo F. (Inactive) made changes -
            Description Original: There is a scheduling bug which results in issues being scheduled for a wrong person and surfaces under the following circumstances:

            * It concerns only sub-tasks having either an assignee in Portfolio or Jira assignees with a Jira assignee level above or equal sub-tasks.
            * There must be a certain number of possible member/sub-task assignments (which resource can be assigned to which sub-task).

            Workaround:
            To work around the problem we can try to reduce the possible assignments of sub-tasks. That means that if each of sub-tasks has either an assignee in Jira or an assignee in Portfolio, the problem will not appear. But obviously this is a tedious workaround.             		New: There is a scheduling bug which results in issues being scheduled for a wrong person and surfaces under the following circumstances:

            * It concerns only sub-tasks having either an assignee in Portfolio or Jira assignees with a Jira assignee level above or equal sub-tasks.
            * There must be a certain number of possible member/sub-task assignments (which resource can be assigned to which sub-task).

            Workaround:
            To work around the problem we try to reducing the possible assignments of sub-tasks. That means that if each of sub-tasks has either an assignee in Jira or an assignee in Portfolio, the problem will not appear.

              Unassigned Unassigned
              pferreira@atlassian.com Paulo F. (Inactive)
              Affected customers:
              4 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: