0
1
copying a Project is simply a pain in the a... (i.e. importing the Tasks),\nmainly because only template Projects can be imported. Consider Project A is in Progress, we acquire a similiar Project. No, A cannot be imported because its Status is not a template (it is still in Progress).\nActually, this is the most common workflow for us. Solution: *Dispaly Project list *Display Project A (there is no edit Icon in Project list) *edit Project A *set Status to template, save *create Project B, Import Tasks from A *Project list *Display Project A *Edit Project A *Set Status back to in Progress, save All that just for copying? Convinced that this is a bad workflow? Only let's hope nobody Forgets to set the Status back, otherwise everybody will complain that Project A is gone/deleted/lost. I understand that template Status for importing was introduced because some users have Project lists that are too Long - but: please put this choice into the Settings: Import from all Project statuses or only from templates. that would make daily work much easier (and less error proof, if someone Forgets to set the Status back. In principle, this is a serious bug if I need to modify A in order to be able to copy it.

asked 13 May '15, 05:32

opto's gravatar image

opto ♦
82341105131
accept rate: 10%

asked 13 May '15, 05:32

Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×25
×1

question asked: 13 May '15, 05:32

question was seen: 399 times

last updated: 13 May '15, 05:32

powered by Bitnami OSQA