Skip to content

Filter by Epic does not see customised Epic issue-type #209

@johnorourke

Description

@johnorourke

Expected Behavior

Using JIRA Cloud. We renamed the "Epic" issue type and have a custom issue schema, but issues still have the 'epic' field.

Actual Behavior

In the filter, only Epics from the default issue schema are available.

Steps to Reproduce the Problem

  1. Rename the Epic issue type
  2. create a custom issue type schema and include your renamed Epic in that
  3. assign the custom issue schema to a project
  4. create an Epic in that project
  5. add a few tasks with their 'Epic' field set to your Epic
  6. add some work logs to those tasks
  7. observe that your epic doesn't appear in the Epic filter on the Chronos screen

Specifications

  • Chronos-timetracker version: 1.5.5-AC
  • OS: Chrome latest on Windows 10, using JIRA Cloud

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions