Useful information includes:

• Business function or organizational role
• Role within the e3 solution
• Permissions or license type
• Team, department, or tenant
• number of affected users,

Examples:

• DLP analysts processing security incidents
• Team leaders reviewing or approving cases
• Administrators managing system configuration
• Business users handling protected information
• Users belonging to a specific organizational unit

Please include:

• Which data, objects, or processes are affected?
• What input is provided?
• Which action is being performed?
• What result is currently produced?
• What result do you expect instead?

Examples:

• A user changes the status of an object.
• Multiple items are selected and processed together.
• A policy or rule is configured.
• Data is imported, exported, or transferred to another system.
• A report, notification, or automated process is triggered. triggered.

In particular, explain:

• how the process is started,
• which settings or inputs are used,
• the individual steps performed,
• and at which point the expected or unexpected behaviour occurs.

For bugs, please provide sufficient detail so that we can reproduce the issue.

Understanding the underlying use case enables us to provide the most appropriate solution and, where applicable, recommend alternative approaches.

Examples:

• to simplify the handling of security incidents,
• to ensure that sensitive data is only accessible to authorized users,
• to comply with regulatory or internal requirements,,
• to generate month-end reports,
• to transfer data to another business application,
• to reduce manual processing effort.

Examples:

• a specific screen or view,
• the administration or configuration area,
• a policy, rule, or workflow,
• a report or dashboard,
• data import or export,
• an interface or integration,
• a database, configuration file, or system component,
• interaction with a third-party application.

Where possible, also specify:

• the affected e3 product,
• the product version,
• the affected component,
• the environment (Production, Test, or Development),
• and any relevant third-party products or integrations.

Helpful information includes:

• date and time of occurrence,
• frequency,
• the point within the business process,
• recent configuration changes or software updates,
• technical or organizational conditions that may influence the behaviour.

Examples of timing:

• during login,
• while saving changes,
• during data import,
• after a status change,
• during a scheduled process,
• after an upgrade or configuration change,
• under high system load.

Examples of conditions:

• only for specific user roles,
• only for specific data types,
• only in the production environment,
• only when using a particular integration,
• only in a specific workflow status,
• only with large volumes of data,
• only with a particular combination of settings.

Where appropriate, include:

• the expected input,
• the expected processing,
• the expected output,
• and the acceptance criteria that define a successful solution.

Examples:

• The operation should complete without errors.
• The change should only apply to a specific user group.
• The exported data should contain all required information in the expected format.
• Processing time should remain below an agreed threshold.
• Existing functionality must not be negatively affected.

Helpful information includes:

• number of affected users,
• affected business processes,
• potential security or data risks,
• available workarounds,
• desired implementation date,
• critical versus optional requirements.

Where possible, distinguish between:

• Mandatory requirements
• Desired improvements
• Optional enhancements

Please describe:

• how they relate to your request,
• which other systems or functions may be affected,
• and whether you have observed any intended or unintended side effects.

Such as:

• screenshots
• error messages,
• log files,
• timestamps,
• sample data (without confidential or production information),
• configuration extracts,
• workflow descriptions,
• mock-ups or functional specifications.