AppColl Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Popular
    • Groups

    Custom Non-Completion States in Tasks

    Product Requests
    2
    2
    154
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      MarkW5689 last edited by

      Currently, a task has a set of default set of states including completion states. Additionally, custom completion states can be created both globally (in the Account Settings) and task specific (in the New/Update task type page).

      My request is to allow for custom non-completion states (both global and task specific). Basically, the custom non-completion states would act the same as "open," like the custom completion states act the same as "completed."

      This would allow for (1) task generation based on a changed state, e.g., generate a "review" task for another user when a draft is complete, (2) allow reports to be generated based on the state, e.g., all the drafts currently with a client, (3) more easily see the state of a task with multiple parts.

      This would save a lot of complexity of breaking tasks into many individual parts that would daisy chain closing/new task creation. It would also limit some of the task "clutter" in the task list.

      1 Reply Last reply Reply Quote 1
      • gregg_appcoll
        gregg_appcoll last edited by

        Hi Mark,

        Thank you for the feedback. This is an interesting idea and something we will pass on to engineering for consideration.

        -AppColl Support

        1 Reply Last reply Reply Quote 0
        • 1 / 1
        • First post
          Last post

        0
        Online

        550
        Users

        336
        Topics

        965
        Posts