Summary: | [OMNIBUS] OPAC Renewal Option | ||
---|---|---|---|
Product: | Koha | Reporter: | Christopher Brannon <cbrannon> |
Component: | OPAC | Assignee: | Bugs List <koha-bugs> |
Status: | In Discussion --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | lisettepalouse+koha, m.de.rooy |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26355 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26357 |
||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 26354, 26355, 26357 | ||
Bug Blocks: |
Description
Christopher Brannon
2020-04-04 16:11:06 UTC
A bug report with four distinct enhancement proposals should be four bug reports, each with a specific and explanatory title. (In reply to Owen Leonard from comment #1) > A bug report with four distinct enhancement proposals should be four bug > reports, each with a specific and explanatory title. +1 Okay, first off, this is an idea of a new feature. While I list three or four specific changes, that all center around the concept of this feature. I COULD file each separately, but then the concept of patron renewal would be obscured. If you still think this should be 3 or 4 individual enhancements, I can do that. But I'm not sure why that is being imposed here when other features are added that change several elements. Would just like to understand the difference so I can be consistent. If the enhancement you describe should be implemented all in one go, then one bug report is fine. The way you worded the description made it sound like there were different aspects which could be implemented separately. Although no enhancement request is guaranteed to be taken up by volunteers, it does increase the likelihood that a volunteer will tackle an enhancement request if it can be broken down into its smallest usable component. The "depends on" and "blocks" fields can be used to link bugs together if one can't be implemented without another. I've broken this down into separate bugs. Look at see also. (In reply to Christopher Brannon from comment #5) > I've broken this down into separate bugs. Look at see also. It is not completely clear to me what you did. Does this report only stay as the omnibus report, or is development here needed too? You could use the dependencies to indicate that. Also note that OPAC Renewal lets me think first of renewing loans, not patron accounts. I feel like there was no bug filed for the fourth option, correct? Have still reformatted to make things a little clearer. |