| Summary: | [server] repo page refers to itself in progress message. | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Susan McCourt <susan> |
| Component: | Client | Assignee: | Malgorzata Janczarska <malgorzata.tomczyk> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | john.arthorne, Szymon.Brandys |
| Version: | 0.2 | ||
| Target Milestone: | 0.2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | 340968 | ||
| Bug Blocks: | |||
|
Description
Susan McCourt
This can go away entirely if we remove the manual step of having to create a link. This message is send back from the server. I'll change it to "Clone complete.", because in our current flow I don't think there's any information more needed. We can do clone only from repositories view, when cloning is finished we are refreshing the repositories list and user may find his new repo in it. Each repository name is a link to folder with its contents, so I think it's really straight forward and no additional explanations are needed. BTW: I really think we should avoid forming messages on the server site based of some knowledge of how client is built. After all someone may create a different client using our API without any "Repositories" page. I completely agree. That message was a very short term fix back when cloning was done in the Navigator and there was no indication of what to do next. done |