How well do the two projects work together?
Status quo: You can link files to OpenProject work packages and vice versa.
You also get a dashboard widget plus search integration.
The most interesting aspect about the integration, IMO, is the upcoming stuff. You can check out the roadmap here and here.
My personal highlights from the roadmap:
- Epic #41400: Create shared folders in Nextcloud and sync user’s permissions
- Epic #41545: Template folder structure for shared project folders
2 Likes
Thank you very much. Do I understand correctly that it only works with files, but not with e.g. Deck cards/boards?
Nice, could you also offer a comparison to our previous projects functionality:
- link talk conversations
- deck boards
- Files and folders (seems clear these are supported)
See overall discussion of ideas here for the top post.
For now the Openproject integration doesn’t support deck boards or a link to talk conversations. I have to admit it would make the integration feel complete if it did. I don’t know about any future considerations regarding this but I am just an outside observer so who knows if there are internal plans to do so.
There is an open issue in OpenProjects community board from last year, asking about how to communicate the relation between OpenProject work packages and Nextcloud Deck cards to the users and if there is anything on the roadmap to clear up the redundancy of tasks between the two platforms. Hasn’t been answered yet.
I found nothing regarding Nextcloud Talk support on the net.
Respectfully, moved the OpenProject discussion here since it is not the same as the projects deprecation discussed here. This is to avoid further confusion about two different topics that only relate in name as opposed to actual functionality. Thanks, and let’s keep the discussion going in their designated threads!
1 Like
Hi everybody, I am Wieland and I am the managing engineer for the OpenProject-Nextcloud integration. Thank you @Daphne for pointing me to the discussion here as I wasn’t aware of it. Most of the discussion on the integration happened so far in OpenProject’s community area. Please feel free to join the discussions there, and please bring your feedback, bug reports and feature requests there so that we use it for planning and adjusting the development roadmap for the integration.
Currently the integration of OpenProject and Nextcloud allows for linking files and folders to work packages. Work packages are tasks, issues, bugs etc. and they are always part of a project. They are used to organize work. The links between work packages and files/folders answer the question “Where are the files for my tasks? And where shall I save my work results so that the next coworker (assignee of the task) can find them?”.
In the next couple of months we will work on the second question: “How can I ensure that all project members have access to the files?”. And we will do it by providing a folder in Nextcloud that is shared with all project members, each one with the rights to read, write, create, delete, reshare as defined by their role(s) within the projects.
I think I am a bit late for the discussion on the old “projects” feature in Nextcloud as I don’t have it on my Nextcloud 25 anymore. However, to me it does not look like a project but rather like a tag. It simply bundles multiple items (files, talks, deck cards) together. That is not a real project in my eyes. From an OpenProject perspective, a project has team members, each one with specific roles and rights. It is a temporary organization of people, work and knowledge.
So if you want to use the integration for replacing the old Nextcloud projects then I would use an OpenProject work package as they can bundle all relevant files/folders by linking them.
We cannot link talks yet, but I am listening if you come up with proposals.
I don’t see any good reason why to combine Nextcloud Deck with OpenProject. If you have OpenProject then you have a fully fledged project management environment, allowing you to have boards, Gantt charts, etc. allowing top-down and buttom-up work flows on the same work packages. Deck (as far as I understand it) is pretty much a subset of it. But please point me to my blind spots if I miss an important use case here.
2 Likes
The idea of incorporating project management software with a live chat has always been intriguing to me ever since Atlassian presented the first prototype of Stride.
Stride made it easy for teams to interact with the respective JIRA and Confluence pages for a given project.
The idea behind Stride was that messages could be marked as Task or Decision (for a project).
I used the beta with a small team and we loved it. I can speak for us all that Atlassian really struck gold here with both the unique selling point and the UX. It lowered the barrier to keep our projects JIRA and Confluence pages up to date. My guess is that this was because we didn’t have to “context switch” between chatting about a project and writing an official work package/documenting a decision.
We were really sad when Slack got involed - just to shut it down. Nothing ever came close to this afterwards.
Maybe there lies some opportunity in the long term relationship with Nextcloud. After the file functionality is done, I would love to see an integration with Nextcloud Talk that picks up on Strides premise.
That being said, a perfect NC Talk integration would feature:
- The ability to subsribe talk conversations to specific projects. Project notifications get pushed to this Talk convo.
- The ability to mark messages as Info, Decision or Task. This could be a great opportunity to synergize with Niels Lindenthals vision for the future meeting module
1 Like
@wielinde, thanks for chiming in.
When it comes to me (and I should assume a few other people too), what we have in NC Deck covers our needs when it comes to tracking/documenting tasks and projects. We’ve been using the NC “Projects” feature to link various resources together, and have all related items displayed.
For what it’s worth, we don’t have a wish to transition to OpenProject, and consequently have a completely new set of infrastructure to manage. All that happened was that the NC Projects feature got dropped by surprise, and we were advised that the OpenProject-NC integration might be suitable to replicate some of the lost functionality.
Turns out, some crucial aspects aren’t covered there, so we wondered whether there’s serious reason that couldn’t be added. However, I would guess we’d all rather just have the NC Projects feature reintroduced (and improved upon) instead.