Problem/Motivation

Is there a way to view all the content created by a task entity? As shown in the images below, when a user navigates to a task URL, it only displays the task details that are shown on the board. Is there a way to ensure that all details can be displayed?


Steps to reproduce

Install the vanilla Burndown module, create a project and a task in the backlog, and then add it to the board. Right-click on the task link; this will navigate to a new tab where you can edit the task entity. Press 'Save,' and it will display a result.

Proposed resolution

Unknown looking for direction on how this could be solved.

Issue fork burndown-3497524

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

purencool created an issue. See original summary.

jeremylichtman’s picture

I think you could do this with Views. i.e. a view that lists all tasks for a project, regardless of status.

purencool’s picture

@jeremylichtman could there be a link added to the card with a view list of one, that shows all the fields attached to the entity task? Currently, the task card has two edit links.

jeremylichtman’s picture

Not sure I understand the ask. What would the display show?

purencool’s picture

Issue summary: View changes
StatusFileSize
new612.2 KB
new776.99 KB

When testing with a Drupal View and a display view on a new installation, it doesn't seem to display all items. Do you have any suggestions on how to get all these items to render?


jeremylichtman’s picture

You may have to add relationships, i.e. for the log.

purencool’s picture

I can get the view to work if I don't render the Task Rendered entity and only use separate fields. What is interesting is that when I try to override the twig template with burndown-task--full.html.twig in the module, Drupal core won't be recognized. If this could be added, it would give developers the ability to alter content in an entity render layout. What steps do I need to take so that this template, and others like it, can be recognized by Drupal Core's rendering API?



jeremylichtman’s picture

Not sure. Can you create a custom display mode for the entity, and use the template for that?

swirt’s picture

I think there are couple changed that would align with how people might be expecting this to behave:

  1. On the cards that appear on the boards, have the edit link icon still go to the edit form (/burndown/task/2/edit), but have the task id link point to the entity view (/burndown/task/2).
  2. Setup entity view to user the "Full Content" view mode. Currently it looks like by default that is still rendering the card twig template but should really be using the full.
  3. Setup the card display to use the teaser view mode.

Would this work? I do have some concerns around backward compatibility, but we could include notes in the release not to alert people that they need to start managing it using the view modes.

jeremylichtman’s picture

I don't have context on what the issue is here, and how it relates to the current version of the module. So not sure.

swirt’s picture

I think the user stories would go like this.

As a user who has View access to Tasks, I would like to be able to click on the card for a task and be able to see all the visible details of the task (all fields marked as visible in manage display for "full content" including comments, so that I may see the task details without needing to have edit permissions.

As a board user, I would like to be able see all details of task, without having to use the edit form, which is less readable and more likely lead to an un-intended modification of the Task.

As a site builder, I would like to be able to control what fields show on the full content Task view and what fields show on the teaser/card view. so that I can provide tasks that meet the needs of my site's users.

swirt’s picture

Screen captures (proof of life) are visible in the MR.

swirt’s picture

Status: Active » Needs review

jeremylichtman’s picture

Status: Needs review » Fixed

Merged, and will push a release in a couple of minutes.

This is very good work. I thought it would be much more complex to resolve.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

swirt’s picture

Status: Fixed » Closed (fixed)