Closed (works as designed)
Project:
Feedmine
Version:
7.x-2.0
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
14 Jun 2013 at 23:16 UTC
Updated:
16 Jun 2016 at 10:41 UTC
Jump to comment: Most recent
Comments
Comment #1
christefano commentedFeedmine is currently designed to submit feedback at the Drupal site level and not the individual Drupal user level. The way we use it is to create a new user in Redmine and add that to the Redmine project where feedback is being submitted to.
The Feedmine block can have any access controls that you'd like, however. You can choose to make it visible only to users with "content staff" or "administrator" roles, for example.
Is individual Drupal user access something that you'd like to see in Feedmine? I'll be happy to review any patches you contribute.
Comment #2
petednz commentedThanks for the feedback. I understand the intention now. It seems like it would be v helpful to be able to get 'some' information about 'who' posted the feedback, otherwise how would you know who to re-assign the ticket to eg for QA after the fix is done.
I will give it some thought. A shortcut might be somehow pre-pending the 'body' of the ticket whe the logged in users name?
Not sure if we will give this enough use to put time in to patching, but will consider it if we find it a really helpful tool.
Comment #3
christefano commentedThe UID of the person submitting feedback is saved to the JSON file that accompanies their submission. This file is attached to the Redmine issue.
Another Redmine module appeared today:
https://drupal.org/project/redmine_issues
I haven't tried it yet but it appears to allow for individual Drupal users to submit and track their own Redmine issues.
Comment #4
petednz commentedThanks for that pointer to the other module - guess you will be watching it closely.
Not sure i understand re the json file - this isn't something that I should see as a file attachment on the Redmine ticket that is created should I? Certainly no file on the ticket i am looking at.
Comment #5
gokulnk commentedThis doesn't seem to be the general use case. If we need to implement this feature, then we will need to have the user level configuration form where they can enter their own API key.
Closing this for now. If anybody else requests for this feature then let us reopen it.