2012-04-20T19:38:32+03:00 The latest version from http://offers.assembla.com/update-site does not work correctly with my eclipse Version: 3.7.2 Build id: M20120208-0800 After installing and restart I'm unable to connect to my space. Pushing "_Validate Settings_" results in: *No Assembla repository found at url: Cannot get space name from url* "_Update Spaces from Repository_" doesn't work either. This applies to http and https. Version: MyLyn Connector: Assembla 1.0.0.201009170054 com.assembla.mylyn_feature.feature.group Assembla Inc 1 19258213 3 false cro_H6Hu4r4iWaeJe5cbCb 30 2 cro_H6Hu4r4iWaeJe5cbCb bn3gVIDG8r3AP8ab7jnrAJ 0 New 0

No Assembla repository found at url: Cannot get space name from url

2012-04-20T19:38:32+03:00 0.0 0.0 Small 1.0 0.0 cro_H6Hu4r4iWaeJe5cbCbMichaelSpMichaelSpMichaelSp aeMflAYaKr27KwaaeP0Qfc 2008-11-07T15:19:47+02:00 A user reported in the forum the following error: http://forum.assembla.com/forums/3/topics/826 The new Mylyn connector for Assembla tickets successfully connects and validates, and can create new tickets and add comments to the tickets it created but no query manages to retrieve the existing tickets, making it completely unusable. Eclipse error log entry follows: <pre> eclipse.buildId=M20080911-1700 java.version=1.5.0_16 java.vendor=Apple Inc. BootLoader constants: OS=macosx, ARCH=x86, WS=carbon, NL=en_US Framework arguments: -keyring /Users/removed/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws carbon -arch x86 -keyring /Users/removed/.eclipse_keyring -consoleLog -showlocation Error Thu Nov 06 17:40:05 EST 2008 Unexpected error org.eclipse.core.runtime.CoreException: Unexpected error at com.assembla.mylyn.core.AssemblaTaskDataHandler.createTaskData(AssemblaTaskDataHandler.java:68) at com.assembla.mylyn.core.AssemblaRepositoryConnector.performQuery(AssemblaRepositoryConnector.java:118) at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeQueriesJob.synchronizeQuery(SynchronizeQueriesJob.java:343) at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeQueriesJob.synchronizeQueries(SynchronizeQueriesJob.java:300) at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeQueriesJob.run(SynchronizeQueriesJob.java:238) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.lang.NullPointerException at com.assembla.mylyn.core.AssemblaClient.getAttachments(AssemblaClient.java:435) at com.assembla.mylyn.core.AssemblaTaskDataHandler.updateTaskData(AssemblaTaskDataHandler.java:385) at com.assembla.mylyn.core.AssemblaTaskDataHandler.createTaskData(AssemblaTaskDataHandler.java:63) ... 5 more </pre> 0 195226 15 false d5sHeK-C0r27W5aaeP0Qfc,aeMflAYaKr27KwaaeP0Qfc 15 3 d5sHeK-C0r27W5aaeP0Qfc bn3gVIDG8r3AP8ab7jnrAJ 4 Test 0

[User Report] Bug when retrieving current tickets

2012-02-20T11:57:29+02:00 0.0 0.0 None 0.0 0.0 aeMflAYaKr27KwaaeP0Qfcakakuninakakuninakakunin d5sHeK-C0r27W5aaeP0QfcsergiosergioSergio RomanoAssembla tanktarta 2012-01-28T13:18:00+02:00 This connector does not handle incoming changes properly. Some things I have noticed include :- 1. Upon creation of a new issue, I am pretty sure it should appear instantly in the query. Internally, these queries are indicated as full=false. 2. If a change is made to a ticket externally, upon the next automatic (or forced) refresh, the query list should show "Incoming changes". Upon opening the task editor and clicking on "Update", the full ticket should be downloaded again. Internally, these queries are indicated as full=false. 3. The connector makes little distinction between partial=false and partial=true. The query should download partial tickets (enough to display all information in the query tree), whereas opening a ticket editor should download all details (downloadTaskData). 4. The connector makes no attempt to use the synchronisation timestamp. This is an optimisation that can signifcantly reduce the amount of data downloaded each time a query is run. After the very first query, every subsequent query requests that the server only return issues that have changed since the provided timestamp. If no issues have changed, nothing should be returned. This will require additions to the REST API to be fully supported. 1 13765013 17 false csvEKa9xOr37IBeJe5cbCb,tanktarta 17 3 csvEKa9xOr37IBeJe5cbCb bn3gVIDG8r3AP8ab7jnrAJ 4 Test 0

Some problems with synchronisation

2012-02-06T15:21:30+02:00 0.0 0.0 None 0.0 0.0 csvEKa9xOr37IBeJe5cbCbtanktartatanktartaBrett Smithtanktarta@gmail.com 2012-01-28T19:03:04+02:00 Proposal for Assembla Mylyn Connector to support automatic time tracking ======================================================================== Mylyn is capable of tracking time spent on any currently Activated tasks. The version of Mylyn included by default in Eclipse only tracks time spent in the IDE itself, although when you have the Tasktop plugins (available for a cost), it can also track time spent outside of Eclipse. The Assembla connector should use this information to automatically update "Work Remaining" and/or "Hours Worked" attributes. The time should not posted until the issue is submitted, at which point any accumlated time will be set back to zero (as there is now a record of it on the server). The work flow would be something like this :- 1. Ticket is created, with a value contained in the "Work remaining" field. 2. Developer is notified of the new ticket, and activates this task in Mylyn. 3. Developer works on the task, all the while Mylyn is recording the amount of time spent. 4. Developer opens the ticket in the rich editor, and sees the "Hours worked" has been set for him, and "Work remaining" has been reduced by the same amount. 4. Developer marks the ticket as complete, and clicks Submit. This submits any changes to the ticket (include change to work remaining). A second API call submits the new "Hours Worked". 5. Mylyn resets the accumulate time to zero. Configuration ============= There are two areas of configuration that will affect time tracking. 1. Window -> Preferences -> Mylyn -> Tasks already has a Time Tracking section. This MUST be enabled for time tracking to work at all. Inactivity timeouts may also be configured here. 2. Per connector configuration. Some users will probably not want this to happen automatically, or they may wish to only increase the "Hours Worked", and not decrease "Hours Remaining". There will be two checkboxes that allow this configuration. User Interface ============== There is a single user interface change in the Rick Task Editor in Eclipse that I believe should be implemented to best support this. The "Working remaining" field should be removed from the Attributes section, and instead placed at the bottom of the task nearer the Submit button. This section will be named "Time Expenditure" to match the analagous section in the Assembla web interface. The section will contain the two fields "Hours Worked" and "Hours Remaining". 1. The "Hours Worked" field is automatically populated with the current "Elapsed Time" from Mylyn's Task Activity Manager. 2. If the task is activated, and there is activity in the IDE, "Hours Worked" will be automatically updated every minute. 3. "Hours Remaining" will initially take the value from the repository. If the task is active, any time accumalated will be subtracted from this value. This behavior will change depending on the configuration options described above. REST API ======== All required functionality is already provided, no server side changes required. 1 13769493 18 true csvEKa9xOr37IBeJe5cbCb 18 3 csvEKa9xOr37IBeJe5cbCb bn3gVIDG8r3AP8ab7jnrAJ 0 New 0

Implement automatic time tracking

2012-01-29T04:19:53+02:00 16.0 16.0 None 0.0 0.0 csvEKa9xOr37IBeJe5cbCbtanktartatanktartaBrett Smithtanktarta@gmail.com 2012-01-29T03:04:45+02:00 In order to to allow custom fields to be edited in tickets, Mylyn needs to know the meta-data for each field. Currently, it appears that this can only be determined using the response from a ticket query. Ideally, Mylyn needs these without doing any ticket queries. I suggest the following :- LIST OF CUSTOM FIELDS ====================== To access the list of custom fields, you need to send a GET request to http://www.assembla.com/spaces/<space_id>/custom_fields If you want to get the response in xml format, be sure to include "Accept:application/xml" in your request header. For example, if you are using curl, you will write: curl -i -X GET -H "Accept: application/xml" http://user:password@www.assembla.com/spaces/my_space_id/custom_fields (Note: http://user:password@www.assembla.com/ is the way you use basic authentication with curl. You need to find out how to use it with your application) RESPONSE: You will get an xml like this: <custom-fields> <custom-field name="Type" type="List" id="11" required="true" hide="false" default-value="List item 1"> <list-value>List item 1</list-value> <list-value>List item 2</list-value> <list-value>List item 3</list-value> </custom-field> <custom-field name="Version" type="Text" id="55" required="true" hide="false" default-value="0.1"/> <custom-field name="Team List" type="Team List" id="66" required="false" hide="false"/> <custom-field name="Date" type="Date" id="99" required="false" hide="false"/> </custom-fields> 1 13783573 19 true csvEKa9xOr37IBeJe5cbCb 19 3 csvEKa9xOr37IBeJe5cbCb bn3gVIDG8r3AP8ab7jnrAJ 0 New 0

Custom Fields

2012-01-29T03:04:45+02:00 7.0 7.0 None 0.0 0.0 csvEKa9xOr37IBeJe5cbCbtanktartatanktartaBrett Smithtanktarta@gmail.com 2012-01-29T03:06:49+02:00 Currently the queries are not very efficient. If Mylyn is configured to refresh automatically (it is by default), then every twenty minutes, ALL queries will be run again in their entirety. Other connectors solve this using the "Synchronization timestamp". 1. First query is run, this uses the current call and sends no timestamp. 2. Server returns ALL tickets covered by the query. 3. Upon succesful completion, Mylyn updates the Synchronization Timestamp, using the current time as the value. 4. Eclipse automatically refreshes the queries (or user forces a refresh). This time, the timestamp is sent along with the query. 5. Server returns only tickets that have changed (in ANY way) since the provided timestamp. 6. Upon succesful completion, Mylyn updates the Synchronization Timestamp, using the current time as the value. 7. Repeat 4-6. This will dramatically reduce the bandwidth taken up by Mylyn clients. Depending on how the server is constructed, there may be advantages in memory and CPU usage as well. 1 13783593 20 true csvEKa9xOr37IBeJe5cbCb,b0e6YOp1yr4BCyacwqjQXA 20 3 csvEKa9xOr37IBeJe5cbCb bn3gVIDG8r3AP8ab7jnrAJ 0 New 0

Query Optimisation

2012-02-06T15:21:30+02:00 7.0 7.0 None 0.0 0.0 csvEKa9xOr37IBeJe5cbCbtanktartatanktartaBrett Smithtanktarta@gmail.com 2012-01-29T03:55:06+02:00 Mylyn has the concept of subtasks, which may be used for duplicates, requires and other dependency types. This maps to Assembla's associations. Mylyn provides some additional user interface for these in the query list, as well as actions to create subtasks in various places. Tasks that have children may be expanded using the tree-like query list widget. To get the best experience, 3 areas must be changed Client Code =========== The client code must be changed to retrieve associations and configure the Mylyn task data model accordingly. Rich Task Editor ================ The rich task editor should be extended to show a new section that has a similar design to the web interface, i.e. a list of task associations detailing the dependency type and status of the linked task. REST API Changes ================ Firstly, the current associations calls return the TICKET ID. However, everywhere else in the API, the TICKET NUMBER is the key used. This will make it very difficult for Mylyn to map associations to the actual ticket. It would be great if associations could include the ticket number as well. The second change is optional, but recommended to avoid additional HTTP calls. Associations are currently not returned as part of a ticket query. In Mylyn it is preferable to have this information available in the bulk query, rather than having to load individual tickets. This will require changes to the REST API. Being as this will add additional data to all queries, perhaps it should be made optional (using a URI parameter, header or alternative path). 1 13789083 21 true csvEKa9xOr37IBeJe5cbCb 21 3 csvEKa9xOr37IBeJe5cbCb bn3gVIDG8r3AP8ab7jnrAJ 0 New 0

Associations Support

2012-01-30T20:23:59+02:00 21.0 21.0 None 0.0 0.0 csvEKa9xOr37IBeJe5cbCbtanktartatanktartaBrett Smithtanktarta@gmail.com csvEKa9xOr37IBeJe5cbCb 2012-02-02T21:15:05+02:00 Mylyn supports grabbing avatar images from Gravatar to show on the rich task editor (and maybe elsewhere). Being as further sources of avatars may be plugged in, and Assembla has avatar images, an "Identity Connector" that supports Assembla should be created. 1 14103463 22 true csvEKa9xOr37IBeJe5cbCb,aMxPg6xuGr3zfBab7jnrAJ 22 3 csvEKa9xOr37IBeJe5cbCb bn3gVIDG8r3AP8ab7jnrAJ 4 Test 0

Show Assembla avatar in editor

2012-02-03T02:31:02+02:00 3.0 3.0 None 0.0 0.0 csvEKa9xOr37IBeJe5cbCbtanktartatanktartaBrett Smithtanktarta@gmail.com csvEKa9xOr37IBeJe5cbCbtanktartatanktartaBrett Smithtanktarta@gmail.com csvEKa9xOr37IBeJe5cbCb 2012-02-02T21:18:48+02:00 Allow custom reports to be chosen as Mylyn queries. Assembla provides API calls to retrive the list of reports, so this should be an easy one. 1 14103673 23 true csvEKa9xOr37IBeJe5cbCb,aMxPg6xuGr3zfBab7jnrAJ 23 3 csvEKa9xOr37IBeJe5cbCb bn3gVIDG8r3AP8ab7jnrAJ 4 Test 0

Support custom reports

2012-02-03T02:46:45+02:00 0.0 0.0 None 0.0 3.0 csvEKa9xOr37IBeJe5cbCbtanktartatanktartaBrett Smithtanktarta@gmail.com csvEKa9xOr37IBeJe5cbCbtanktartatanktartaBrett Smithtanktarta@gmail.com csvEKa9xOr37IBeJe5cbCb 2012-02-03T03:20:15+02:00 Custom statuses may be configured on Assembla, but the Mylyn connector does not take any notice of these. 1 14123923 24 false csvEKa9xOr37IBeJe5cbCb,aMxPg6xuGr3zfBab7jnrAJ 24 3 csvEKa9xOr37IBeJe5cbCb bn3gVIDG8r3AP8ab7jnrAJ 4 Test 0

Support custom statuses

2012-02-03T21:40:51+02:00 2.0 2.0 None 0.0 0.0 csvEKa9xOr37IBeJe5cbCbtanktartatanktartaBrett Smithtanktarta@gmail.com csvEKa9xOr37IBeJe5cbCbtanktartatanktartaBrett Smithtanktarta@gmail.com tanktarta 2012-02-04T03:05:23+02:00 Mylyn can do rich editing of Wiki text. The problem is, Assembla uses a slightly different syntax to those supported by Eclipse WikiText. I could not find out how to create custom wiki syntax implementations. The closest syntax I can find is Confluence. So, by translating between Confluence and Assembla when loading and saving tickets, the wiki editor features may be used. 1 14244633 25 false csvEKa9xOr37IBeJe5cbCb,aMxPg6xuGr3zfBab7jnrAJ,tanktarta 25 3 csvEKa9xOr37IBeJe5cbCb bn3gVIDG8r3AP8ab7jnrAJ 4 Test 0

Translate Wiki formatting in Description and Comments

2012-02-04T03:05:44+02:00 1.0 1.0 None 0.0 0.0 csvEKa9xOr37IBeJe5cbCbtanktartatanktartaBrett Smithtanktarta@gmail.com tanktarta 2012-02-05T14:19:18+02:00 It would nice if it was possible to enter and query daily/weekly scrum reports from Eclipse. * Add a button to the task list view (or elsewhere) to open today's report for the current user. If there are multiple Assembla repositories configured, show a chooser. * If the report already exists, download the existing details. * Use the Rich Task Editor for entering scrum details. This will show 3 LONG_RICH_TEXT editors, for work todo, work done and roadblocks. * Upon Submit, send the report to the server, either updating the current one or creating a new report. * Add ability to create queries that download current/previous scrum reports. 1 14271373 26 true csvEKa9xOr37IBeJe5cbCb,tanktarta 26 3 csvEKa9xOr37IBeJe5cbCb bn3gVIDG8r3AP8ab7jnrAJ 4 Test 0

Stand Up Report support

2012-02-05T20:36:43+02:00 7.0 7.0 None 0.0 0.0 csvEKa9xOr37IBeJe5cbCbtanktartatanktartaBrett Smithtanktarta@gmail.com 2012-02-06T23:03:32+02:00 1. Hide Milestone attribute if tool not installed 2. Hide Attachments if documents tool not installed 3. Hide Permission attribute if support tool not installed Look for others. 1 14349423 27 false csvEKa9xOr37IBeJe5cbCb 27 3 csvEKa9xOr37IBeJe5cbCb bn3gVIDG8r3AP8ab7jnrAJ 4 Test 0

Use space tools API call to determine what features to enable in Mylyn

2012-02-07T01:03:22+02:00 3.0 3.0 None 0.0 0.0 csvEKa9xOr37IBeJe5cbCbtanktartatanktartaBrett Smithtanktarta@gmail.com csvEKa9xOr37IBeJe5cbCb 2012-02-07T01:39:40+02:00 This means Mylyn can highlight due or overdue tasks. 1 14359013 28 false csvEKa9xOr37IBeJe5cbCb,tanktarta 28 3 csvEKa9xOr37IBeJe5cbCb bn3gVIDG8r3AP8ab7jnrAJ 4 Test 0

Make use of milestone due date if one is available

2012-02-08T03:07:02+02:00 1.0 1.0 None 0.0 0.0 csvEKa9xOr37IBeJe5cbCbtanktartatanktartaBrett Smithtanktarta@gmail.com csvEKa9xOr37IBeJe5cbCbtanktartatanktartaBrett Smithtanktarta@gmail.com 2012-02-14T23:18:43+02:00 This will bring the possibility of using the same code for other Java clients. 1 14993763 29 false csvEKa9xOr37IBeJe5cbCb 29 3 csvEKa9xOr37IBeJe5cbCb bn3gVIDG8r3AP8ab7jnrAJ 4 Test 0

Separate REST API client code from Mylyn core

2012-02-15T01:54:50+02:00 0.0 0.0 None 0.0 0.0 csvEKa9xOr37IBeJe5cbCbtanktartatanktartaBrett Smithtanktarta@gmail.com 2012-04-26T14:23:14+03:00 When a ticket has any reference to the "Anonymous" user, either in the comments, or created by/assigned to fields, the sync will fail with the following error: Error 404 "Not Found" in request http://www.assembla.com/user/best_profile/bgfq4qA1Gr2QjIaaaHk9wZ?format=xml An exception stack trace is not available. 1 19902873 30 false d5QOw-ctur4yTTacwqjQYw 31 3 d5QOw-ctur4yTTacwqjQYw bn3gVIDG8r3AP8ab7jnrAJ 0 New 0

Error 404 when synching a ticket with references to Anonymous

2012-04-26T14:23:14+03:00 0.0 0.0 Small 1.0 0.0 d5QOw-ctur4yTTacwqjQYwstefaan.vanderheydenstefaan.vanderheydenstefaan.vanderheyden aeMflAYaKr27KwaaeP0Qfc 2008-09-12T22:37:40+03:00 Allow user to "preview" edited description & comment 0 139924 2 false aeMflAYaKr27KwaaeP0Qfc 9 5 aeMflAYaKr27KwaaeP0Qfc bn3gVIDG8r3AP8ab7jnrAJ 1 Accepted 0

Extended Task-Editor: Preview for Description & Comments

2010-08-24T12:18:22+03:00 2.0 2.0 None 0.0 0.0 aeMflAYaKr27KwaaeP0Qfcakakuninakakuninakakunin aeMflAYaKr27KwaaeP0Qfcakakuninakakuninakakunin aeMflAYaKr27KwaaeP0Qfc 2008-09-12T22:39:36+03:00 New verison of MyLYn (3.0) has some sort of Wiki-Integration. I did not investigated it yet - so, don;t know what it will allow us - and how much time it may take. 0 139930 1 false aeMflAYaKr27KwaaeP0Qfc 11 5 aeMflAYaKr27KwaaeP0Qfc bn3gVIDG8r3AP8ab7jnrAJ 1 Accepted 0

Wiki Integration

2010-08-24T12:18:22+03:00 0.0 0.0 None 0.0 0.0 aeMflAYaKr27KwaaeP0Qfcakakuninakakuninakakunin aeMflAYaKr27KwaaeP0Qfcakakuninakakuninakakunin aeMflAYaKr27KwaaeP0Qfc 2008-09-12T22:51:05+03:00 Allow user to select tasks by many criterias (like in Report Generator in Assembla) This task depends from API, available as REST service 0 139936 12 false aeMflAYaKr27KwaaeP0Qfc 12 5 aeMflAYaKr27KwaaeP0Qfc bn3gVIDG8r3AP8ab7jnrAJ 0 New 0

Extended Task-Query

2010-08-24T12:18:22+03:00 16.0 16.0 None 0.0 0.0 aeMflAYaKr27KwaaeP0Qfcakakuninakakuninakakunin aeMflAYaKr27KwaaeP0Qfcakakuninakakuninakakunin