Describe the bug
A user submitted user support requests regarding there is no option in portfolio selection box when creating a new initiative.
As the "anonymise" option is ticked when submitting a user support request. We cannot find out who is the sender and the corresponding institution for investigation.
Finally I did a checking in backend databsae table user_feedbacks. Column user_id contains the user ID who submitted the request.
I use the user ID to trace which user and institution, realised that there is no profolio created yet.
I replied email to suggest user to create a profolio then it will be showed in profolio selection box when creating a new initiative.
No feedback received from user. I did a checking after a few days, a profolio and initiative have been created in that institution already.
I assume that user issue has been resolved.
Possible improvements
If the "anonymise" option is ticked, column user_feedbacks.user_id should be null. To make sure we are doing what we do.
By default, user support request should untick the "anonymise" option.
My Institution > Portfolio > Help text for "Institution Portfolios", we should show the help text all the time. To increase the possibility that user to read it.
Describe the bug A user submitted user support requests regarding there is no option in portfolio selection box when creating a new initiative.
As the "anonymise" option is ticked when submitting a user support request. We cannot find out who is the sender and the corresponding institution for investigation.
Finally I did a checking in backend databsae table user_feedbacks. Column user_id contains the user ID who submitted the request. I use the user ID to trace which user and institution, realised that there is no profolio created yet. I replied email to suggest user to create a profolio then it will be showed in profolio selection box when creating a new initiative.
No feedback received from user. I did a checking after a few days, a profolio and initiative have been created in that institution already.
I assume that user issue has been resolved.
Possible improvements
Screen shots
Related email RE Bug Submitted.zip