Story #2890: As an authenticated user, I can see what resource(s) a task acted on. - Pulp

Actions

Send by e-mail Copy link

Story #2890

closed

As an authenticated user, I can see what resource(s) a task acted on.

Added by daviddavis over 7 years ago. Updated about 4 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

Category:

Sprint/Milestone:

Start date:

Due date:

% Done:

Estimated time:

Platform Release:

Groomed:

Sprint Candidate:

Tags:

Sprint:

Quarter:

Related issues

Actions

Copy link

Updated by daviddavis over 7 years ago

For more info, see the proposed implementation at https://pulp.plan.io/issues/2482#note-11

Actions

Copy link

Updated by daviddavis over 7 years ago

Blocks Story #2891: As an authenticated user, I can search for a tasks based on what resource they acted on. added

Actions

Copy link

Updated by regularuser about 7 years ago

What url will the detail view of the TaskResource be?

Actions

Copy link

Updated by daviddavis about 7 years ago

bmbouter I wasn't thinking of providing one—at least not for the MVP. I'm assuming there won't be any information on the task resource other than the task FK and the resource FK so exposing the join model didn't seem necessary.

Actions

Copy link

Updated by bmbouter about 7 years ago

I added a checklist item about offering filtering along with this change. For the feature to be complete I think it needs filtering.

Also what will the name of the FK attribute be for the Task to show the related TaskResource objects? I imagined it would be called 'resources' but then that could be confusing between the 'created_objects' perhaps? I think I liked the name 'tags' better since it more clearly identifies it as metadata about a task (I think). That would suggest that the new TaskResource should be called TaskTag or Tag and then the related_name attribute on Task would be called Tags once again. @daviddavis that an improvement or a step backwards?

Actions

Copy link