Paul - We don’t have that level of access to jira config. This is infra at ASF. So, we must use our internal processes.
Thanks On Fri, Mar 14, 2025 at 10:11 AM Paul <pchristi...@gmail.com> wrote: > Yes, Adam James > That aligns with several "best practice" methods. But the root cause > culprit is the label name . . . "Fix Versions" which may (but shouldn't) > be interpreted to mean; "Which version needs the fix?" > > *1. Suggestions to cure: * > > - *(should be easy) Field Description:* > - Modify the "Fix Version" field description within Jira. Make it > explicit and unambiguous. > - Example: "Issue Resolved Version" > - *(also easy, if your can find it) Help Text/Tooltips:* > - Use Jira's built-in help text or tooltips to provide more > detailed instructions when a user hovers over the "Issue Resolved > Version" > field; > - such as: This field is completed AFTER the fix is available to > users and shows release / version has the fix in it." > - *(more complicated and often has unintended consequences) Enty > Rules:* > - If allowed with subscription, create rule(s) preventing editing > until the issue reaches X stage. > > > -- > -- > Paul >
