Optimize displaying dates in CLI

Bug #1379681 reported by Renat Akhmerov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-mistralclient
New
Medium
Nikolay Makhotkin

Bug Description

Do we need to remove dates (created at, updated at) for actions, workbooks, workflows? Can we remove them by default and enable with using '-c'?

Changed in python-mistralclient:
importance: Undecided → Medium
assignee: nobody → Nikolay Makhotkin (nmakhotkin)
Revision history for this message
Anastasia Kuznetsova (akuznetsova) wrote :

Why do we need to remove dates? It helps up to identify which actions(workbooks, workflows) are new, which were updated and which are not

Revision history for this message
Renat Akhmerov (rakhmerov) wrote :

The assumption is: if we just created a new object and didn't update it yet then created_at date will contain milliseconds. Need to confirm.

Changed in python-mistralclient:
milestone: none → kilo-1
Changed in python-mistralclient:
milestone: kilo-1 → kilo-2
Changed in python-mistralclient:
milestone: kilo-2 → kilo-3
no longer affects: python-mistralclient/kilo
Revision history for this message
Anastasia Kuznetsova (akuznetsova) wrote :

@Renat,
We still can see "Created at" and "Updated at" columns during creation, update of items.
Does it mean that bug is not actual anymore?

no longer affects: python-mistralclient/liberty
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.