Task Name Prefix Inconsistency - Duplicating Projects

Oh hi, I'm back with more feedback.

I've encountered a weird inconsistency in how the task name prefix displays, depending on how the project is created.

When a project is created from a request form, the task name includes the prefix inside brackets, then a space, then the original task name.

However, when duplicating a project from the workspace (ie, right-clicking a project and selecting "Duplicate"), the task name will have the prefix (with no brackets), then a space, then the original task name.

Naturally, this just makes things more complicated when viewing tasks from multiple projects, because there will be two sets of alphabetized project lists (depending on whether the task name prefix included brackets or not).

What is the reason for this? Is it something that can be customized or made consistent?

Thank you!
Carolanne

Upvote 18
9 comentários
Spot On Innovative Approach Stellar Advice

Similarly, when duplicating a project (from either the request form or workspace), having the prefix always followed by a space is very inconvenient. It prevents us to create our own custom prefix+structure. In our case, we wanted to have a WBS-like numbering, where the template project and its subfolder and subtasks were pre-numbered, and have the duplication allow us to add project number precede the sub-items :

 

  • Prefix : PA.007.
  • Template task or folder : "1.3 - Risk management"
  • Expected output : "PA.007.1.3 - Risk management"
  • Observed result : "PA.007. 1.3 - Risk management". Notice the space between the "7." and the "1.3".

 

 

Having an option to not append a space by default to any prefix would be great.

Also, +1 on the problem of the request form putting prefix between square brackets, without possibility of customizing the prefix integration with the template items' name.

4
Spot On Innovative Approach Stellar Advice

@Stephanie, just checking in regarding this weird issue too. Any solutions on the horizon?

1
Spot On Innovative Approach Stellar Advice

This!  So frustrating that the format of the prefix is inconsistent.  When will this be fixed?  Also troublesome is that when you add a prefix from a request form it does NOT prefix the Title or top level task/project name.  BUT...when you duplicate a project and use a prefix it does it at all levels!  Can we just have it work one way?  

1
Spot On Innovative Approach Stellar Advice

The inconsistency is also troublesome for our team. I wish the request forms would leave out the brackets. Not sure why anyone would want the brackets, they make thinks look so clunky.

 

2
Spot On Innovative Approach Stellar Advice

Hi Everyone,
In addition to this, the prefix brackets create trouble with mail integration (formatted mail subject to update tasks).

The square brackets are treated conventionally as parent location title or specific status or dates parameters. Therefore having them in prefix confuse the mail integration and create new folders instead of update existing ones. 

Would be great if the prefix brackets could either be deleted or replace by parenthesis in order not to corrupt an interesting feature of Wrike.

When testing the parenthesis, it perfectly works. 

0
Spot On Innovative Approach Stellar Advice

Ashvind CURPEN

Would love to see these removed as well!

I don't think parenthesis are the solution either. When exporting reports Wrike uses (#) around their numbers to count the number of tasks or projects on each line. It is always a pain trying to remove those numbers especially when users tend to name projects and use parenthesis to call out text in project names.

0
Spot On Innovative Approach Stellar Advice
Avatar
Hugh

Hey everyone! Thank you for this feedback. It's been passed on to the Product team.

I don't have an update for you, but as soon as I do, I'll let you know!

0
Spot On Innovative Approach Stellar Advice

9 months since the last update.  Any advancement on this?

0
Spot On Innovative Approach Stellar Advice

Hi Eric, welcome to the Community, and thank you for posting. 

Please allow me to share a little detail on how we process Product Feedback. If you'd like to find out more, this article explains what happens after we receive Product feedback. 

We check with our team and assign a status after a thread receives more than 60 upvotes according to our Product Feedback Guidelines & Statuses. This suggestion at the moment needs more support. In the meantime, if there are any updates in relation to this suggestion, we'll be sure to update you here.

Please let me know if you have any questions.

Cansu Community Team at Wrike Wrike Product Manager Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

Cansu Wrike Team member Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

0

Folllowing List for Post: Task Name Prefix Inconsistency - Duplicating Projects
[this list is visible for admins and agents only]

Alto
Didn’t find what you were looking for? Write new post