jyoungman please provide more details about the failure you're seeing and the conditions surrounding the failure. Two sentences do not provide enough information for others to assist you.
You've provided a very brief description of what you're seeing but no description of the context around the issue, the things you've investigated, or the things that you've discovered while exploring the issue.
In an open source community (even more than in a business), an issue report needs to be more filled with insights about your exploration rather than containing a single "photograph" of the current state. An issue report that is processed by volunteers (like most open source projects) needs to contain enough information that those volunteers find enough motivation in the description to provide assistance. Many volunteers want their donated time to help as broadly as possible. Your description is not enough that anyone else can assist you.
Some things that might inspire others to want to assist:
- Describe the last version that worked (assumed to be before 2.277.1)
- List the plugin names and versions installed (see "How to report an issue")
- Upload the job definition that fails to save parameterized data
- Confirm that you've performed the steps described in the Jenkins 2.277.1 upgrade guide and in the Jenkins 2.277.1 upgrade webinar
- Describe the experiments you've tried and their results
Frequently, collecting that information will discover a solution to the problem faster than posting an incomplete issue report and hoping someone will help you.
jyoungman please provide more details about the failure you're seeing and the conditions surrounding the failure. Two sentences do not provide enough information for others to assist you.
You've provided a very brief description of what you're seeing but no description of the context around the issue, the things you've investigated, or the things that you've discovered while exploring the issue.
In an open source community (even more than in a business), an issue report needs to be more filled with insights about your exploration rather than containing a single "photograph" of the current state. An issue report that is processed by volunteers (like most open source projects) needs to contain enough information that those volunteers find enough motivation in the description to provide assistance. Many volunteers want their donated time to help as broadly as possible. Your description is not enough that anyone else can assist you.
Some things that might inspire others to want to assist:
Frequently, collecting that information will discover a solution to the problem faster than posting an incomplete issue report and hoping someone will help you.