Group workflow feature? about netbout HOT 9 CLOSED

migrated from Trac, where originally posted by marko_lipo on 15-Sep-2010 9:34pm

Source ticket: #14

from netbout.

migrated from Trac, where originally posted by yegor256 on 16-Sep-2010 3:30pm

That's exactly what netbout.com is for - to organize only groups on demand. Every bout is a micro instance of Trac, which you don't need to setup, configure and maintain. You just create it with one click, and you get a shared space of documents online, you keep history, versions, discussions, etc.

The only feature that is not yet explained in the SRS is a possibility to join bouts into working communities. For example 5 people are working in the same company and they want to share contacts and bouts. This would be an interesting feature, but I'm not yet clear about its scope. Any ideas?

from netbout.

migrated from Trac, where originally posted by marko_lipo on 19-Sep-2010 1:54pm

Frankly, I'm full of ideas, just have to think over (or sleep over) and structure them :).
When you mentioned that every bout is a micro instance of Trac, it crossed my mind that we have example in our Trac. From my point of view, on example of this project, as I joined project after there were around 20 tickets created and various ideas shared so far, it was a bit complicated for me to connect all information, as they were scattered within various tickets, and types of ticket.
So am I correct if we say that bout'' is ''ticket type'' as it is now in Trac? And ''tag of the bout is every ticket belonging to same type?

So if we were using NetBout in our project, then Risks' would be one bout, 'Defects would be another etc, and tags would be tickets?
Pls feedback am I thinking in right way?

from netbout.

migrated from Trac, where originally posted by yegor256 on 19-Sep-2010 4:30pm

You're getting closer, but let me correct a little.

Trac is a powerful instrument (like Bugzilla, Mantis, JIRA, and others) and it can't be replaced for bug tracking. Netbout is not going to replace Trac. Netbout is going to enable people to use functionality similar to Trac, but in a more simplistic application. Please, review the user story I added to [wiki:SRS@11], I'm sure it will help.

Tag is a folder. If I have 50 bouts - it means I have 50 conversations going on now. With 50 separated groups of people (of course, some people may participate in several groups). 50 is too many for me in one batch. I want to manage them somehow. And I attach tags to them: "family", "programmers", "about new business ideas", etc. Every bout can have a number of tags attached at the same time. It means that one bout may be in more than one "folder" at the same time.

from netbout.

migrated from Trac, where originally posted by marko_lipo on 19-Sep-2010 11:19pm

OK thanks for clarification.
I didn't mean that NetBout will replace Trac. Just wanted to compare their features.
So bout is conversation with certain subject or topic, in which there could be many messages exchanged between participants...
Each participant could create tags and attach them to the bouts.
Tags are used for grouping bouts and for searching for bouts and/or users.

Coming back to my previous comment with parallel to Trac. I would say that tickets in Trac are like bouts in NetBout, with many messages/comments attached while tags are free to be defined by each user on his own level.

Coming back to the working group feature, I think it is necessary to introduce sharing option to the NetBout, and group feature to the users. So users should mutually agree to form a group, and then to define shared bouts visible to all of them?

from netbout.

migrated from Trac, where originally posted by yegor256 on 20-Sep-2010 2:15pm

Absolutely, we're on the same page now.

Regarding the group feature you mentioned, it can be easily implemented just by inviting people to existing bouts. For example, I want you "to share" my bouts. I invite you into them. And you become one of their participants. No need to have groups, just invite people or kick them off. That's how I see the process.

from netbout.

migrated from Trac, where originally posted by marko_lipo on 8-Oct-2010 11:33pm

I agree. How I see it, for the purpose of let's say project team support, there would be necessary to have some helpers invoked: calendar with deadlines and/or expected dates to deliver, for example. If you agree we can close this ticket.

from netbout.

migrated from Trac, where originally posted by yegor256 on 11-Oct-2010 4:50pm

Yes, exactly. Calendar is a good example of a helper, which can help small groups.

from netbout.

migrated from Trac, where originally posted by yegor256 on 23-Nov-2011 9:06am

Milestone JUN11 deleted

from netbout.