#777: User restriction to only tickets they open?
--------------------------+---------------
Reporter: mbrownnyc | Owner:
Type: enhancement | Status: new
Priority: major | Version:
Resolution: |
--------------------------+---------------
Summary:
I would like to give end users the ability to create tickets.
I would like to restrict each user to only see tickets they have opened
(or followed).
I would like a user's workflow to be as follows:
1) User access bloodhound site
2) user logs on (authing with LDAP)
3) user is either greeted with "new issue" page, or with the list of their
current tickets.
Thanks!
Robusto:
[08:25] <mbrownnyc> I would like the infrastructure team to be able to
open tickets, and associate them with a project
[08:25] <mbrownnyc> but I would like only tickets they open be visible to
them
[08:25] <mbrownnyc> (for instance)
[08:26] <mbrownnyc> also front line support has no issue tracker, and I
would like users to be able to open tickets by accessing bloodhound simply
[08:26] <mbrownnyc> so none of those users would be able to see any
tickets but their own
[08:26] <allegary> interesting
[08:27] <mbrownnyc> also, can you confirm that bloodhound can use trac
"plugins" (interested in email related issue management, and LDAP auth)
[08:27] <mbrownnyc> at my last place I used redmine for this whole thing
[08:27] <mbrownnyc> but bloodhound seems to be a bit of a better choice
[08:27] <allegary> we are attempting to maintain the ability to use trac
plugins
[08:28] <mbrownnyc> i don't deal with software engineering here, nor did I
there
[08:28] <mbrownnyc> so i suppose it is an interesting use case :)
[08:28] <mbrownnyc> cool... I believe I saw plugins that do both of those
things I mentioned
[08:28] <allegary> that is good
[08:28] <mbrownnyc> any idea if the role based access as it exists will do
what I'd like?
[08:29] <allegary> though if we have not already looked at them, they may
need some extra work on our part to get them working
[08:29] <mbrownnyc> cool
[08:29] <mbrownnyc> I'll see as I move forward
[08:30] <allegary> so, I think that you will probably be able to restrict
with role based access as you say if I understand it
[08:30] <allegary> per user might be a bit more interesting
[08:30] <mbrownnyc> I'm less concerned with the infrastructure team, but
the users simply won't use the system if it's complex
[08:30] <mbrownnyc> they'll continue to email, and then no one can track
issues, and produce reports
[08:30] <allegary> yeah
[08:31] <allegary> hmm
[08:31] <allegary> I should try to get backup into this conversation!
[08:31] <mbrownnyc> do you think I can work out a workflow like: user
accesses URL, user logs on with LDAP creds, use either sees list of opened
issues, or user is greeted with "new issue"?
[08:32] <allegary> I have not seen such use before
[08:33] <allegary> I don't *think* that would currently be possible
[08:33] <allegary> might be worth raising a ticket with us to ask for it
[08:34] <mbrownnyc> cool, will do
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/777>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
