[Koha-bugs] [Bug 4461] Context-sensitive report a problem screen

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4461

--- Comment #43 from Aleisha Amohia <aleisha at catalyst.net.nz> ---
(In reply to Jonathan Druart from comment #42)
> I have attached few follow-ups, pick the ones you need/want.
> 
> However I am a bit at lost here.
> 
> There is no UI so far, but we have such things:
> +        status varchar(1) NOT NULL default 'N', -- status of the report.
> N=new, V=viewed, C=closed
> 
> so the status will never be updated, what will happen when we will have the
> UI?
> 
> IMO we should bring the UI with that patchset, and remove the notice. Do we
> really want the notice to be sent? If yes, do we really want the new table?
> :)

As mentioned in multiple earlier comments, once this is pushed I want to add a
follow-up feature where staff can manage problem reports on the intranet. The
original report for this feature asked for an email to be sent so that's what I
implemented. Up to the community if they would prefer the email notice version
or the staff-side management version, but I don't see any harm in having both.

> 
> Also, do we really need the problem_reports.recipient DB field if we have
> the email?
> Same for username? We have the borrowernumber.
> 
> About the DB structure again, it seems that status should be an ENUM.

Agreed that some of these fields are redundant, and status can be an ENUM.
Happy to make these changes.

-- 
You are receiving this mail because:
You are watching all bug changes.