Demand Workspace in vanilla Brazil PDI - questions re. some functionality
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi Folks,
I've been playing around with the latest Demand next experience Workspace in Brazil PDI and have some concerns, maybe anyone could provide some feedback here. I don't know if my PDI is missing something/broken or that is indeed what it's supposed to look like.
1. No Demand Name/Title - It is not displayed in list view and when creating new Demand via the "New" button, the only fields shown are Category, Type and Dates.
When going to Details view, Name is also missing in the form. Even in backend default view, name is missing.
2. Same with Demand number. I would expect that in most of companies both Number and Name are critical attributes allowing to identify a specific demand.
I believe 1 and 2 might be a bug?? If not, leaving this out is puzzling.
3. Demand Type is mandatory from the very beginning. But maybe at this point DM does not yet know what the Demand would be converted to. IT may require deeper analysis, checking financials etc. Funny thing is, at the end of OOTB Demand Playbook we have the option to change the Type. So why make it mandatory right at creation?
4. The OOTB Playbook suggests that Demand might be automatically converted to EAP entity - in my case, when I went through the Playbook till the end, the conversion had to be done manually. Is there any config OOTB that would do this automatically?
5. No State is displayed on newly created Demand, There is only 1 UI Action visible related to state "Reset to Draft". But how should I know in what state I am currently? Again, feels like a bug? The Playbook also does not allow to check the state of the demand.
6. Team does not appear anywhere in the Details form - OOTB only on the default playbook, there is a step to provide a team, but it is not mandatory. Without a specified team, the Epic will not be visible anywhere in EAP. On backend view, Team appears in a dedicated EAP Details section, but again, non-mandatory. Perhaps this should have been made mandatory to select if Type is one of EAP entities. Furthermore, I can select any Team, not only the one aligned to the specific EAP config level (e.g. when creating EAP Epic, I can select a Team which is linked to Feature or Story level - feels like there should be a reference qualifier to restrict that).
Hoping that SN Team or others will be able to provide feedback to the above. Many thanks!
