Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for teams #580

Closed
Aditya94A opened this issue Feb 20, 2020 · 22 comments
Closed

Add support for teams #580

Aditya94A opened this issue Feb 20, 2020 · 22 comments
Labels
core Changes regarding core concepts feature New feature or request

Comments

@Aditya94A
Copy link

Postman teams for postwoman.

More details in #507 (which is sort of a prequel for this issue)

@liyasthomas
Copy link
Member

liyasthomas commented Feb 20, 2020

Noted. Currently we have support for individual account and sync. Teams is next priority 🚀

@liyasthomas liyasthomas added core Changes regarding core concepts feature New feature or request labels Feb 20, 2020
@liyasthomas liyasthomas added this to the v2.0 milestone Feb 20, 2020
@liyasthomas liyasthomas pinned this issue Mar 3, 2020
@car520120
Copy link

request non ajax url is ok? Submit url to get results? For example get url: http://www.yandex.com

@zhangzhaohong
Copy link

What time could you merge the code about the ability of creating a team?

@liyasthomas
Copy link
Member

Track progress here: #879

@liyasthomas liyasthomas unpinned this issue Sep 27, 2020
@ziaulrehman40
Copy link

Following this issue for long time, eagerly waiting for this thing.

@tttao7
Copy link

tttao7 commented Jan 17, 2021

Following this issue for long time, eagerly waiting for this thing.

Me too !!!

@dalexanco
Copy link

Hi :)
I really love hoppscotch, the approach is modern and agile.
But hoppscotch is a different product than postman and it should stay different.
With postman, they are trying to make money and their team feature is the best way to do it.
They designed it with this goal in mind.

But I don't think it's the best opportunity for hoppscotch...
I found many references to draw.io in other comments and for me, that is the best path for hoppscotch : sync files with a local/cloud folder.
Let the storage provider handle the team feature (local git repository, shared folder on google drive...).

I read the hoppscotch code, I understand that the project is growing at a point that it's become harder and slower to add features. I'm afraid to see it becoming too complex for features that does not rely to request management. I mean, handle teams is an open door to : ACL, file conflict management and it make hoppscotch attached to a backend.

Please keep this project as we love it : simple and not attached to a specific platform (github or firebase).

That was the humble opinion of a regular hoppscotch user (and probably a futur contributor :D)

@AndrewBastin
Copy link
Member

Hi @dalexanco,

Thank you for sharing your thoughts. We have already thought about many of the points you brought forward.

We are already almost done with Teams and we are introducing our own backend architecture to support it.

We have a couple of reasons for choosing a self-hosted backend architecture over the other options.

We wanted to keep the Teams features easy to use and adopt. As per our research and experimentations we found out that the experience (using files) seemed a bit lacking. We want to bring in the ability to sync up changes and work as frictionless as possible. With the self hosted backend we are able to introduce an effortless experience with more features like access control and permissions and this also allows us to introduce more fine-grained controls later on.

But at the same time, we are looking into secondary solutions as well to provide better experience and still provide a file based implementation. With the File System API and similar web stuff on the horizon and gaining support we will eventually be able to bring it forth and utilize.

As of now though, we are working on a overhauling of the state system to allow for implementing a proper Workspace feature which allows you to bring in and export your entire Hoppscotch configuration as a file which can load and switch to from. There is also significant work going on to try implementing a native app.

Thank you for using (and loving!) Hoppscotch. We are trying our best to support independent features but at the same time we want to uphold our philosophy of being an easy to use and quick platform that people can leverage to test, build and implement APIs on.

We are looking forward to seeing your awesome contributions!

@shadiramadan
Copy link

@AndrewBastin is there a status update or ETA on teams?

@AndrewBastin
Copy link
Member

AndrewBastin commented May 13, 2021

@AndrewBastin is there a status update or ETA on teams?

Hopefully in the coming days! Just some minor bug fixes remaining

Maybe even tomorrow 😙

@liyasthomas
Copy link
Member

liyasthomas commented May 15, 2021

Hi everyone,

Today we're excited to announce that the most awaited "Teams collaboration" feature is now out for Beta users.

Join Hoppscotch Teams β waiting list now →

We'll be accepting 100 users per week ❤️

Screenshots

Shared Collections

screely-1621069504004

Save request to Teams collection

screely-1621069546645

Teams list

screely-1621069621039

Edit Team roles

screely-1621069645910

More updates coming soon 🚀

Closing this issue on behalf of #1641

@ziaulrehman40
Copy link

This is cool @liyasthomas , the most awaited feature, finally made it in! You guys are awesome 🎉

Any timeline/plan (even tentative) for its final release out of beta?

@liyasthomas
Copy link
Member

If everything goes alright - probably within a week.

@AndrewBastin
Copy link
Member

I would like to use this opportunity to thank, @oshhh @IshaGupta18, @rohanrajpal and @raghav0307 for their amazing work on helping make Teams a reality! They worked on the implementation of Teams in the Hoppscotch web app.

Thank you so much guys! 🥰

@rohanrajpal
Copy link
Contributor

I would like to use this opportunity to thank, @oshhh @IshaGupta18, @rohanrajpal and @raghav0307 for their amazing work on helping make Teams a reality! They worked on the implementation of Teams in the Hoppscotch web app.

Thank you so much guys!

It was a great learning experience. Loved working on it.

@davew94
Copy link

davew94 commented Jun 1, 2021

Have been eagerly waiting for this feature for a while and great work for delivering. Any news on how beta has went and when this will be moved into production?

@liyasthomas
Copy link
Member

@davew94 we're working on delivering the best experience for our users. Please join the beta program and give us your feedbacks.

You can expect the Teams feature release in couple of weeks.

@OnekO
Copy link

OnekO commented Oct 19, 2021

So, as I can read, there will not be Teams in self-hosted applications?

It's understable that everybody wants to make money from their work, but as a lover of postwoman/hoppscotch it's a bit sad. Will be a firebase backend merge request welcomed?

Thanks for your great job.

@liyasthomas
Copy link
Member

@OnekO there'll be Teams support in self-hosted instances.

@OnekO
Copy link

OnekO commented Oct 19, 2021

@OnekO there'll be Teams support in self-hosted instances.

So good then, waiting to test it. Thx!

@liyasthomas
Copy link
Member

Teams are now out of closed beta.

✅ Unlimited teams

✅ Unlimited shared collections

✅ Unlimited team members

✅ Role-based access control

✅ Cloud sync

✅ Multiple devices

Read more

@binaryfire
Copy link

@OnekO there'll be Teams support in self-hosted instances.

Hi. Just wondering if this has changed? It’s been almost 12 months since the closed beta ended and it’s still not available for self-hosted instances

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Changes regarding core concepts feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.