-
Notifications
You must be signed in to change notification settings - Fork 20
Design Ideas
andrewtobin edited this page Feb 24, 2012
·
6 revisions
http://home.jenkinsfamily.com.au:8000/guestAuth/app/nuget/v1/FeedService.svc
Should allow:
- To enter account details: Name/Email, Password, ApiKey
- Most commonly used Group/Repository?
- Option on if it should create tasks when uploaded
- Option on if it should email tasks to people assigned when uploaded
- A button on the email header that opens up a pre-populated screen
- That screen will fetch users Groups and Repositories (should cache?)
- For the selected Repository it should fetch the labels used and colours
- If possible fetch who has access to that repository to allocate it to
- All fetching to be done using async
- Check Github screen, but anything that can be uploaded should be.
- Text of issue should be a header saying who/when sent the email, followed by the text of the email
- Should be editable (for review/details).
- When saving the task should we save a simple task, or a complex task based off a rendered issue?
Fogbugz screenshot for reference
- As for submitting Issues (editable, header, etc) but should be a comment to an existing, open issue.
- Sync down recent pull requests as tasks
- Keep a cached value of last sync to compare
- Links back to the Pull Request in the task
- Should we download the PR diff like Github for Windows does and display it in the Task?
- or should we just allow that to go through email as normal, should we sync back to tasks?