Identify who created the lighthouse ticket.
We've had some confusion in a couple instances where someone created a lighthouse issue from a tender ticket but we couldn't figure out who. It would be helpful to identify the logged in user that created the ticket.
Discussions are closed to public comments.
If you need help with Tender please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Will on 09 Mar, 2009 12:54 PM
I agree. I'll mention this to the dev team today.
2 Posted by rick on 10 Mar, 2009 08:04 AM
The integration is still a little bare bones. Ideally we'd store a key for every user so that the ticket is created in their name. However, this also greatly complicates how the settings are stored in the database.
We thought about doing something where we set the user_id of the ticket, but I feel like this sets a dangerous precedence where users are able to spoof tickets as other users.
3 Posted by bkayser on 13 Mar, 2009 03:51 PM
Just to clarify I was less concerned about the identity in the
lighthouse ticket (which I assumed was problematic) than I was about
identifying who submitted it in the Tender ticket. You can't tell
looking at the Tender ticket which Tender user hit the link to open
the lighthouse ticket.
I was hoping it would be simple to indicate in the Tender issue what
user submitted it to lighthouse.
As for the lighthouse ticket--I'm sure you considered this--it would
help even if in the text of the ticket you could indicate the tender
user, without changing the actual user id. It wouldn't need any
additional configuration, but maybe that's problematic for other
reasons...
4 Posted by rick on 14 Mar, 2009 03:14 PM
Just added this, it should be pushed over the weekend sometime. It now tracks a user_id on Tender's Ticket model.
rick closed this discussion on 14 Mar, 2009 03:14 PM.