Community

Welcome 🖖

Hi there! 🙂 Want to become a black belt Wrike Ninja? Here's how to earn a Wrike badge

Welcome 🖖 Have you checked out this week's Release Notes yet?

Hey! 👋 Curious about something? Visit How To to search and ask the Community for answers.

Welcome! 👋 Figured out a good tip or trick? Share it in Best Practices.

Want to connect your existing software to Wrike? Learn and ask how in the API section.

What can we help you with?

e.g. Gantt chart, Creating tasks, Sharing folders...

Custom fields in tasks and subtasks

16 comments

  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Anastasia

    (Edited )

    Hi Jens, thank you for sharing this feedback! Is the main problem here overall related to the Custom Field just being visible in the Project Info and taking up space there?

    Is this helpful? 2
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Beth Narunsky

    We have the same issue.  Only use Tasks but need custom fields for each task created.  

    Is this helpful? 3
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Lauren Cooke

    Yes it would be nice to at least hide a field from the Project Panel like in table view you can hide columns, it would be nice for the project panel to mirror that. 

    It would also be great to just have custom fields on a task level. 

     

    Is this helpful? 2
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Stephanie Westbrook

    Hi everyone, thanks for your feedback here! I'm going to go ahead and move this post to our Product Feedback section so that others can upvote it. 

    Stephanie Westbrook Community Team at Wrike 🌎Discover... Wrike Discover and become a Wrike expert. Click here to get started

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Ty LaStrapes

    I have the same need.  😁

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Indran Naick

    You could do this by adding a dummy folder with the fields you need in tasks defined and then just tagging the task to that folder.  The tasks will then inherit those fields.  Newish to wrike so I'm not sure about the implications, would be interested to know if anyone else used it this way.

    Is this helpful? 3
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Aljaž Gorjup

    We have same issue: for example we have project (product) where we would need general product data (custom fields) and then tasks (delivery) with data for that specific delivery (custom fields). It would benefit us greatly if this would be implemented.

    Is this helpful? 3
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Ryan Okelberry

    Definitely need this too! There are times when we want to track task-specific metadata. Would be a big plus. Another extension of this would be that I can only find a way to update a custom filed associated to a task from a request form. Why can't a request form also update custom fields that are only associated to the project or folder?

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Stephen

    I really like @Indran's workaround here - has anyone else tried this yet?

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Tuomo Suominen

    (This might be a slihgtly different request, but) I would need project level custom metadata to be inherited to task level. Currently, I use blueprints to create new projects, and I can only fill out project-level metadata at that point. However, I need to have that same metadata available on task level in order to run dashboards and reports on those tasks, so I now also need to fill out the custom fields on task level. It would be a great relief to have the (option?) to inherit project level custom metadata down to task level.

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Al Sape

    Yes fully agree, this would help get tasks more flexibility, the "issue" use case is similar to my use of tasks for Agile development, would similarly mark them as "bugs," etc.  While I'm very happy Projects and folders can have custom fields, it would be nice if they also could not have them!

    Thanks.

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Antoine Ancelin

    Hi, fully agree. We have the same need!

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Nick Etten

    I was surprised to learn that this wasn't a part of current functionality.  I can create custom fields for projects; projects and folders; and projects, folders, and tasks; but I can't create custom fields for just tasks or just folders.

     

    This would be great to have implemented For reporting and tracking purposes for our team.

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Hugh

    Hey everyone, thank you for all your feedback here! It's been passed on to the Product team. I don't have an update at the moment. If anything changes, I'll be sure to let you know.

    Hugh Community Team at Wrike 🌎Discover... Wrike Discover and become a Wrike expert. Click here to get started

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Ryan Okelberry

    This continues to be left out of improvements. My comment to this was 9 months ago. We adopted custom fields back with "old table" view originally when they came out. Then the only way to add a custom field was from the table view. It's now been interesting to learn how a task adds up all the custom fields that it could potentially have access to based on the folders the task may be tagged into. This can become a large list, if your custom fields have been set up on higher level folders. Tasks end up having custom fields that don't necessarily even apply. We've had to restructure our custom fields to be associated to the lowest level folders possible, so as to minimize the accrual of custom fields associated to a task, that it picks up from parent folders.

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Lisa

    Hi everyone! I've spoken with the team again, and they are planning to review the custom field logic. Once we have any updates, we'll make sure to get back to you. Thanks for sharing your feedback! 

    Lisa Community Team at Wrike 🌎Discover... Wrike Discover and become a Wrike expert. Click here to get started

    Is this helpful? 1
    Comment actions Permalink

Please sign in to leave a comment.

Folllowing List for Post: Custom fields in tasks and subtasks
[this list is visible for admins and agents only]

Community

Welcome 🖖

Hi there! 🙂 Want to become a black belt Wrike Ninja? Here's how to earn a Wrike badge

Welcome 🖖 Have you checked out this week's Release Notes yet?

Hey! 👋 Curious about something? Visit How To to search and ask the Community for answers.

Welcome! 👋 Figured out a good tip or trick? Share it in Best Practices.

Want to connect your existing software to Wrike? Learn and ask how in the API section.