Project

Profile

Help

Task #2636

closed

Planning: design pulp3 approach to task tags.

Added by jortel@redhat.com almost 8 years ago. Updated about 4 years ago.

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

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

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


Related issues

Is duplicate of Pulp - Task #2482: Planning: design pulp3 approach to task tagsCLOSED - COMPLETEdaviddavis

Actions
Actions #1

Updated by jortel@redhat.com almost 8 years ago

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

Actions #2

Updated by jortel@redhat.com almost 8 years ago

  • Tracker changed from Issue to Task
  • % Done set to 0
Actions #3

Updated by ttereshc over 7 years ago

  • Status changed from NEW to CLOSED - DUPLICATE
Actions #4

Updated by ttereshc over 7 years ago

  • Is duplicate of Task #2482: Planning: design pulp3 approach to task tags added
Actions #5

Updated by daviddavis over 5 years ago

  • Sprint/Milestone set to 3.0.0
Actions #6

Updated by bmbouter over 5 years ago

  • Tags deleted (Pulp 3)

Also available in: Atom PDF