Epic in Project - new project workspace - button "new" in the related tab "epic"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello,
Why is there a "New" button in the "Epics" related tab on the "Details" page in the new project workspace?
As I understand, epics are connected to a project through stories.
However, if we create an epic using this button, it doesn’t seem to make sense, since neither the epic nor the stories under it are linked to the project.
Additionally, the epic record does not have "Project" or "Project Phase" fields.
This is confusing for the users and makes the process feel inconsistent.
Is this an expected behavior?
Thanks in advance for any clarification or insights.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi,
OOTB this related list is omitted when there is no associated records. The 'New' button is also omitted. Potentially some one has customised it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi,
Thanks for your reply.
To make sure this was not caused by customization, I verified the behavior in a clean PDI (Zurich version). In the out-of-the-box configuration, when a Project is set to Hybrid or Agile, the Epics related tab is visible on the Project Workspace → Details page, and the New button is available there as well.
However, I also noticed that this behavior seems to be specific to the new Project Workspace. In the classic backend view of the Project form, the Epics related list does not provide a New button.
From a data model perspective, this is a bit confusing. The Epic record does not contain a reference to the Project or Project Phase, and when an Epic is created from this related list (related tab in PW), neither the Epic nor the Stories created under it are automatically associated with the Project.
Because of this, it seems unclear how creating an Epic from the Project Workspace is expected to work in practice. My understanding was that the relationship between Projects and Epics is typically established indirectly through Stories.
So I would like to clarify whether:
• This is the expected out-of-the-box behavior in Project Workspace
• Or if Epics are generally expected to be created from the backlog / Agile hierarchy instead of directly from the Project
From a user experience perspective this can be confusing, since the related tab suggests a direct relationship that is not actually enforced in the data model.
Any clarification on the intended design would be appreciated.
