Skip to content
This repository has been archived by the owner on Feb 23, 2020. It is now read-only.

tests_selenium_admin.py:360-361: Fix missing "Tags" field... #405

Open
0pdd opened this issue Jan 25, 2019 · 1 comment
Open

tests_selenium_admin.py:360-361: Fix missing "Tags" field... #405

0pdd opened this issue Jan 25, 2019 · 1 comment
Labels
1 hour typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i 2 performer can implement issue at his closest convenient time cleanup everything that do project stronger, flexible, reusable Tags feature take it any teammate can take this issue and start working with it

Comments

@0pdd
Copy link
Collaborator

0pdd commented Jan 25, 2019

The puzzle 317-e1224271 from #317 has to be resolved:

stroyprombeton/stroyprombeton/tests/tests_selenium_admin.py

Lines 360 to 361 in 4a4a837

# @todo #317:60m Fix missing "Tags" field selenium admin tests.
# It not appears as table column when selected in the list with fields.

The puzzle was created by @duker33 on 25-Jan-19.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.
@0pdd
Copy link
Collaborator Author

0pdd commented Jan 25, 2019

@artemiyds2 @duker33 please pay attention to this new issue.

0pdd referenced this issue Jan 25, 2019
@duker33
#fix Skip selenium test (#402)
4a4a837
This was referenced Jan 25, 2019
Closed
Closed
@duker33 duker33 added 1 hour typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i take it any teammate can take this issue and start working with it cleanup everything that do project stronger, flexible, reusable Tags feature 2 performer can implement issue at his closest convenient time labels Jan 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
1 hour typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i 2 performer can implement issue at his closest convenient time cleanup everything that do project stronger, flexible, reusable Tags feature take it any teammate can take this issue and start working with it
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@duker33 @0pdd