Project

Profile

Help

Task #2636

Planning: design pulp3 approach to task tags.

Added by jortel@redhat.com about 3 years ago. Updated about 1 year ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

0%

Platform Release:
Blocks Release:
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Sprint:

Description

Design pulp3 approach to task tags. Derive the tags Instead of having a method on every model.


Related issues

Duplicates Pulp - Task #2482: Planning: design pulp3 approach to task tags CLOSED - COMPLETE Actions

History

#1 Updated by jortel@redhat.com about 3 years ago

I propose using the resource name (model class) and build the ID part of the tag using the natural_key_fields.

#2 Updated by jortel@redhat.com about 3 years ago

  • Tracker changed from Issue to Task
  • % Done set to 0

#3 Updated by ttereshc about 3 years ago

  • Status changed from NEW to CLOSED - DUPLICATE

#4 Updated by ttereshc about 3 years ago

  • Duplicates Task #2482: Planning: design pulp3 approach to task tags added

#5 Updated by daviddavis about 1 year ago

  • Sprint/Milestone set to 3.0.0

#6 Updated by bmbouter about 1 year ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF