Goal event name can be empty

[Barbaracwx]

I am able to leave the goal event name empty. If the goal event name is empty, how do I find the goal event name?

[soc-se-bot]

Team's Response

Accepted, will fix it! Product is still usable, proposed severity of Medium from High.

Items for the Tester to Verify

:question: Issue severity

Team chose [severity.Medium] Originally [severity.High]

• [x] I disagree

Reason for disagreement: The severity of this issue might initially seem medium as the product remains functional, allowing the goal event name to be left empty. However, the repercussions of an empty goal event name have significant implications, potentially escalating the severity to a high level.

Primarily, the bug directly impacts the core functionality of the system, hindering the ability to retrieve or identify specific goal events with no names. When attempting to use the 'find' function to locate these events, the absence of a name renders the search ineffective. This leads to a critical loss of functionality as users are unable to effectively search for or distinguish between different events lacking names.

Furthermore, the possibility of having multiple events with no names creates ambiguity and confusion within the system. If multiple goal events share the characteristic of having no names but differ in dates, start times, and end times, it raises questions about the integrity of the data. Users might encounter difficulties discerning between these events, potentially resulting in erroneous actions or misunderstandings.

This situation could also pose challenges in data management and organization. It becomes unclear how these unnamed events are handled within the system. Are they considered identical or distinct? The lack of clarity regarding the treatment of events with no names poses a risk of data inconsistency and complicates the usability and reliability of the system.

Hence, while the product might remain usable on a basic level, the critical impact on functionality, data integrity, and user experience warrants an elevated severity level. Resolving this issue is imperative not just for ensuring a functional 'find' feature but also for maintaining a clear and organized database of events, preventing potential user confusion, and upholding the overall reliability and usability of the system.

---