this is under internal discussion. it's not especially easy to implement, but it's fairly high on our wish-list.

@nickhilliard any further information about internal discussions about this one?

@nickhilliard any further info about this one? The PR has been submitted but yet to be accepted. Is there any information from your internal discussions I could combine into the PR to get this feature merged?

not yet unfortunately. We've been working on a framework upgrade (doctrine->eloquent) over the last several months. This has a huge change footprint, so for the moment we're staying away from feature-adds and anything which needs database schema modifications.

Ah okay, this makes sense. Perhaps we can look at this feature as a way to test the benefits of the new framework?

Is there a timeline on a dev cut of the framework migrations?

Hopefully reasonably soon, but that's a vague answer. @barryo?

The change is very big and encompasses the entire database layer. I just caught up with @yannrobin there and he's powering through it. In fact most objects are done but the trickier ones are left: auth, users, some of interfaces, patch panels. I think an estmiate of four weeks would be reasonable (but that's not me giving @yannrobin an arbitrary deadline here, just trying to put a reasonable guess on it).

Thanks all, this is very exciting. Let me know if there is anything you need (testing etc.) closer to release time that we can assist with.

Thanks @tardoe - we'll likely do this as a beta release. We'll have it live at INEX first so others will know it's in production use but the beta tag will reflect the stong possibility of UI bugs, etc. We'll be looking for people to give it a go then. Thanks!

@barryo Any update on this one?

@barryo @nickhilliard any update on this?

@tardoe @barryo have you had any progress here? This is something we'd like to implement and we've been waiting patiently for this to be implemented

Has there been any movement on this @nickhilliard or @barryo?