Issue Summary

Yearly Goals (Objectives on Theme Level) have only a n:1 relation to Themes.

Current implementation / observed behavior

1 Theme can contribute to a single 1 Yearly goal - since the implementation is a drop-down element in the Theme GUI.
The implementation in the Theme is not an objective list as it is on the lower hierarchy layers for Epics, Features, and Stories.

Current functionality:

• n Themes can contribute to 1 Yearly goal
• 1 Theme cannot contribute to nYearly goals

Expected functionality:

• n Themes can contribute to 1 Yearly goal
• 1 Theme can contribute to n Yearly goals

It should be a m:n relation as in all the hierarchy layers below (Portfolio, Program, Team)

Why should this be a m:n relation?
(1) it is very natural, that 1 Theme contributes to multiple yearly goals (Yearly goals describe what we like to achieve in this year as an organization which is the desired outcome, Themes describe the desired output we develop in the SW Teams)
(2) it is very natural, that 1 Theme contributes to multiple-year goals over a lifetime, since the Themes likely span over years.
(3) it is also very likely that multiple themes contribute to 1 yearly goal.

The result of (1) + (2) + (3) is a m:n relation.
 

Steps to Reproduce

1. Select or create a theme
2. Assign a 'Yearly Goal', see the attached image. (Only 1-yearly goal can be selected)
   

Expected Results

Multiple yearly goal can be selected and associated with a theme

Actual Results

Only 1-yearly goal can be selected and associated with a theme

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available