project board #843
project board #843
Conversation
|
I started looking this over yesterday but didn't finish. This morning, I realized that the "research" I'd promised which looked at how the GitHub and GitLab APIs represented Kanban is STILL on the computer at home. The essence is: There shouldn't be a lot of operations changing columns on a board once they've been set up, but there will be a ton of adding and moving bugs around the columns, so caching should really help there. I had also looked at Github Projects and that's a whole different data structure (I'm assuming out-of-scope WRT Kanban). In any case, |
Isn't that just a board with some form of transition rules?
You mean that the board itself should support being "closed" ? |
|
Projects can be cross-repository, so I think it's structurally similar to a board but how would the importer handle this? I also got the impression that it was possible to add cards to columns that weren't issues but it's been a few months and I'd have to look again. I'd be happy to be proven wrong too! And yes, at least on GitHub you can mark boards as closed. I can take a look at the JSON I saved when I get back to my other computer on Monday. Better yet, I can attach the JSON to this repository for referen 8000 ce. |
Import multiple remote repo within the same local git repo? |
c7b11ef to
c1aad31
Compare
94deb22 to
386f3f8
Compare
1507092 to
dcb4df0
Compare
731c38e to
2892cf8
Compare
c760b75 to
bb4139d
Compare
|
Any status on this one? |
Also rework of entity generic interfaces, in a way that allows to handle low level or cache entities the same way (ReadOnly), and another ReadWrite interface that also allow to mutate the entity. This should fix some long long standing issue around that, and notably fix the resolvers. This is the first time an entity really load another one, which is what required that fix. Hopefully this opens the way for Identities to use the dag framework.
No description provided.