Story #11968
Ext JS 4.0 integration
Status: | Closed | Start date: | 2011-05-03 | ||
---|---|---|---|---|---|
Priority: | Won't have this time | Due date: | |||
Assigned To: | - | % Done: | 75% |
||
Category: | - | Spent time: | - | ||
Target version: | Sprint 7 | ||||
Story points | - | ||||
Velocity based estimate | - |
Subtasks
History
#1 Updated by Sebastian Kurfuerst over 4 years ago
- Position deleted (
1) - Position set to 7
#2 Updated by Sebastian Kurfuerst over 4 years ago
- Position deleted (
8) - Position set to 10
#3 Updated by Sebastian Kurfuerst over 4 years ago
- Position deleted (
10) - Position set to 14
#4 Updated by Robert Lemke about 4 years ago
- Project changed from Core Team to Base Distribution
- Target version deleted (
788)
#5 Updated by Sebastian Kurfuerst about 4 years ago
- Target version set to Sprint 8
- Position deleted (
17855) - Position set to 1
#6 Updated by Sebastian Kurfuerst about 4 years ago
- Status changed from New to On Hold
see the comments on #26598 for reasons we're postproning the migration until we have some more bugfix releases of ExtJS.
Thanks Regine for trying it out!
#7 Updated by Rens Admiraal about 4 years ago
- Subject changed from Ext JS 4.0 integration (if available) to Ext JS 4.0 integration
- Status changed from On Hold to Accepted
#8 Updated by Sebastian Kurfuerst almost 4 years ago
- Status changed from Accepted to Closed
Bulk-closing issues because they are
- not relevant anymore due to the sproutcore based backend
- or already implemented in the meantime.
Regards, Sebastian
#9 Updated by Robert Lemke over 3 years ago
- Target version changed from Sprint 8 to Sprint 7