Skip to content

Timeline additional issues #2301

@vic-georgiev

Description

@vic-georgiev

Ok, here are several issues that I'm going to capture in a list. @acshields @vikasrohit @RishiRajSahu please break them between releases and importance.

Current implementation
screen shot 2018-08-06 at 10 08 04 am

Designed
screen shot 2018-08-06 at 10 08 12 am

The goal of this is to ensure the customer has selected all the checkpoint winners to continue to the final stage.

screen shot 2018-08-06 at 3 41 16 pm

Expected
screen shot 2018-08-06 at 3 42 32 pm

What would be a better content to explain next steps in the project and get customers moving? Research with Sales.

Starts as "Add link"
screen shot 2018-08-06 at 4 36 50 pm
and switches to "Add a link".
screen shot 2018-08-06 at 4 36 56 pm

Please use consistent labeling in both cases (@acshields please advise on language). You're adding 1 link at a time (thus I would say "add a download link" to initiate the process, and "Add link" in the expanded state to drive the interaction.

  • Remove specification milestone duration (timeline starts). When we have a timeline start most of the time we don't want to set a timeline for the customer to complete a specification. The goal is to flip the switch once the specification is ready and the copilot can start the challenges on the platform. We already made the specification document optional, so let's remove further constraints from the system and make sure that the first checkpoint is the agreement on specification, which would record the start of work and transition into the next milestone in the timeline. Remove specification milestone duration (timeline starts) #2412

  • Remove delivery milestone duration (timeline ends). Once the work is done we do a deliver as a single point in time, and the customer has no further option to extend/expand request for fixes. The delivery literally marks the end of the phase and provides a link (or links) to the customer to download their artifacts/deliverables. Remove delivery milestone duration (timeline ends) #2413

  • Design checkpoint button should be enabled only if you have:

  • Review state of the milestone is really separate thing. Each review has 2 days to be completed. For the sake of simplicity we combined the work and the review into a single milestone. Once we complete the work, the review time starts. Right now this is not clear from the button label. (check the screenshot above). Better separation of review work and review milestones #2414

  • Remove messages for adding a phase to a project plan. This is done by managers and makes no sense as I can see what I've just added. The customer can't see a phase when it is in draft state (as added) and it makes no sense to dispatch this message.
    screen shot 2018-08-06 at 2 51 25 pm Remove messages for adding a phase to a project plan #2415

  • Remove the "submit for review" button as our project scope has the exact same data from project creation. This makes no sense at the moment. We're going towards a state where all the project scope data would be submitted at one step and once project is completed it would be ready for review (generate project plan) Remove the "submit for review" button from project scope #2417

  • Hide $0 as cost/estimate from the customer. Our customers should only see data that is relevant. [60$] Hide 0$ as cost/estimate #2418

  • Do not display project status bar twice on the Project Scope tab. This makes no sense (Hide one of the two progress bars). @acshields I'm leaving you to pick which one of the progress bars should stay. I would probably hide the big progress bar as the jump from the sidebar to the main space would be too much). [$20] Do not display project status bar twice on the Project Scope tab #2419

  • Hide project status from customer. We build the new progress bar at the moment and it would be sufficient for communication. The project status should be visible for managers and copilots. Also - let's make sure we tackle the logic of switching project status based on the dependent phase status. Hide project status from customer #2420

  • Rename Channels and Posts to Discussions to keep things consistent.
    screen shot 2018-08-06 at 3 45 06 pm Rename Channels and Posts to Discussions  #2421

  • Make sure the welcome post for a new project actually makes sense. The current scope section doesn't have additional data to submit, and we don't want our customers to reach out to support via email. Changing welcome post for newly created project until scope page doesn't have additional fields to submit #2479

Coder the Bot2:17 pm
Hello, Coder here! Your project 'App design sample test project' has been created successfully. For your next step, please head over to the Scope section and answer all of the required questions. If you already have a document with your requirements, just verify it against our checklist and then upload it. Once you're done, hit the "Submit for Review" button on the Specification. Get stuck or need help? Email us at support@topcoder.com.

Aha! Link: https://topcoder.aha.io/features/TCCONNECT-288

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions