-
Notifications
You must be signed in to change notification settings - Fork 136
Description
Ok, here are several issues that I'm going to capture in a list. @acshields @vikasrohit @RishiRajSahu please break them between releases and importance.
The goal of this is to ensure the customer has selected all the checkpoint winners to continue to the final stage.
What would be a better content to explain next steps in the project and get customers moving? Research with Sales.
Starts as "Add link"

and switches to "Add a link".

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:
- less than 5 designs to select
- selected 5 designs out of a 6+ options available. [60$] Enforce minimum design selection at checkpoint review milestone #2410
-
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.
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
ChannelsandPoststoDiscussionsto keep things consistent.
Rename ChannelsandPoststoDiscussions#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.
-
Implement the visual notification for new items on a phase (red dot). The customer doesn't have a way to spot when there is a new post or change on the timeline on the phase card at the moment, as it is collapsed. Add notification visual cues to phase timeline tab #2455
-
Make sure the customer can see the currently active phase card. By design we wanted to expand the currently active card to display the timeline when the customer loads the dashboard and project plan (save a click to the customer). [$35] Showing expanded view (with timeline tab selected) of active phase(s) for customer #2478
-
Do not make a welcome post to the phase discussion (Posts tab) before the phase is active. Even then it would be nice to actually have a post from the copilot and a more meaningful message depending on the type of the phase. Right now the message doesn't help the customer to do anything, and is a noise for the manager. Handling phase discussions tab for drafted phases #2477

-
User avatar in the post composer (footer) is not aligned with the avatar from the actual post. [$35] Align user avatar in the post composer correctly #2480

-
Extension can't be requested during design review. Please remove the button while we're in review. [$30] Remove extension request for under review milestones #2481
-
After editing a milestone properties, the hover state still persists. I have to hover over the milestone to remove the highlight. [NOT REPRODUCIBLE]


-
Design links URL should be aligned to the right and 30px from the widest text element
design link name. Right now the checkpoint and final design links URL are not uniform (they should). [$20] Align design links correctly for design related milestones #2482

-
Post formatting is missing: [$35] Post contents - link & mention styling #2201
- Links (should be blue)
- @mention - (should be bold)
-
@mentionshould not lead to the profile page; let's remove the profile link - we don't want customers to go to the community profile page at this time. [$20] Post mention should not be link #2476 -
Final fixes add a new line button looks wierd [$40] Correcting final fixes
Addbutton styling #2484

-
When an additional design is selected, removing one of the first 3 placements keeps the selected state (blue) of the previously "additional" element [$35] Correctly handle selected design link's background colour #2490

-
Links are not editable once the delivery is completed, but they should be. What would happen if a copilot moves things after they've completed adding links, and there's an error? Keep the option to edit/remove links for manager/copilots/admins at all times. @acshields FYI [$40] Allow editing link for final deliverable #2492
-
When a place was selected (final designs), do not allow more places to be selected within the same design. To reproduce: make sure you have 5 designs, select paces from 1 to 3, select an additional design, remove first place: [$50] Do not allow more places to be selected within the same design. #2577

-
Checkboxes are not using the standard border (or it seems like it) [$20] Checkboxes are not using the standard border #2578


-
Adding link for final fixes button text is different in states. [$20] Adding link for final fixes button text is different in states. #2580
-
Restore Coder the Bot avatar. It's gone missing somehow. [$30] Restore Coder the Bot avatar #2576




