Problem/Motivation

As a task owner it would be nice to have a block available to me that shows all non-closed tasks I am assigned to.
It should group them by "On board" and "In backlog" and sort them by priority. (high priority on top...)
It put them in a bulleted list with links to the actual task.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork burndown-3610981

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:

About issue forks

Comments

swirt created an issue. See original summary.

jeremylichtman’s picture

jeremylichtman commented

I'd suggest doing this in a page, not a block, particularly if it includes backlog tasks (which may be extremely numerous).

An alternative would be a block that shows a few sorted by priority (desc), with a "more" link at the bottom to a page showing all.

Edit: If the "page" is actually a view, then this could be click-sortable (and filterable) as well.

swirt’s picture

swirt
he/him
Primary language English
commented

Good idea about it being a View.
It would need a hook_update_n to deploy it to existing installs.

swirt’s picture

swirt
he/him
Primary language English
commented
Title: Add a "my tasks" block » Add a "my tasks" View pages
Assigned: Unassigned » swirt

swirt opened merge request !45

jeremylichtman’s picture

jeremylichtman commented

Looks good so far.

The legacy hooks things reminds me that I'll need to work in D12 compat at some point.

swirt’s picture

swirt
he/him
Primary language English
commented
Status: Active » Needs work

Tested this in the Tugboat preview. Something is not working right. the new Views are there, but they are not showing any tasks. I'll have to figure out what's wrong with that.

swirt’s picture

swirt
he/him
Primary language English
commented

This is tested both on a new install vanilla drupal and an update on an existing site.

The perms are not perfect yet because it does not use any of the dynamic project specific perms but there is not a Views only way to pull that off just yet. Will need to do this with an access handler.. I don't want to have to try to roll that out after this View launches, so I am going to block this on that requirement.

swirt’s picture

swirt
he/him
Primary language English
commented
Assigned: swirt » Unassigned
Status: Needs work » Needs review

jeremylichtman’s picture

jeremylichtman commented
Status: Needs review » Fixed

Released on 1.0.68.

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.

jeremylichtman’s picture

jeremylichtman commented
Status: Fixed » Closed (fixed)