AT:
→ When a user selects the Process Instance Duration View (min,avg,median or max) another button becomes available that is called “Process Instance Part”
→ When a user clicks on this button an overlay opens, displaying a UI similar to the branch analysis view
→ The two flow nodes that the user chose, will be part of a sentence that is shown in a UI element that looks similar to a flow node filter, but is placed at the position of the process instance part button (the button disappears when the user has chosen a process part)
→ When user selects process part, we filter the instances that have executed the flow nodes (in backend and add information in the docu).
→ The user can group by all possibilities that we have for process instance duration
→ When a user changes the Process Definition (or version) the process part selection is removed automatically

User Stories:
Users of Optimize NEED A WAY TO find out about the average duration between two defined points in the process (e.g. a start event and a milestone) grouped by start date
BECAUSE this information helps them to monitor time spent on a certain part of their process and see if changes they implemented helped reducing this value.

Users of Optimize NEED A WAY TO find out about the average duration between two defined points in the process (e.g. a start event and a milestone) and be able to compare them with a defined target value
BECAUSE it could help them to find out if they are executing the part fast enough.

Users of Optimize NEED A WAY TO find out about the duration between two defined points in the process (e.g. a start event and a milestone) and be able to compare them with a defined target value per single process instance
BECAUSE it could help them to find instances that are above the duration target and subsequently find out based on data why they are above target (e.g. by using cockpit).