Open sanbornsen opened 6 years ago
My 0.02€ on that: inside of Planner, we only allow the contextual creation of WIs. But we will need, at some point, something that allows creation of WIs outside of the Planner. An example would be a generic "customer issue reporting form" that can be embedded into a customer application. But that kind of forms would also be contextualized because it would make assumptions on the space, the WIT and possibly other attributes as well.
So for now, we don't allow non-contextualized creation of WIs.
@sanbornsen Sudipta, currently as per use case, even Stack Report hits Planner API for creating work items.
Just to update, Stack report creates work item of the type 'Bug'. (As per payload - 'type': 'workitemtypes')
@arunkumars08 have you tried the Stack Report work flow with a SCRUM template?
@nimishamukherjee - verified and its working as expected for Scrum template as well.
@arunkumars08 have you tried the Stack Report work flow with a SCRUM template?
@nimishamukherjee @arunkumars08 and I did talk about this a while ago on mattermost and I think @arunkumars08 has implemented a solution in this PR which is already merged: https://github.com/fabric8-ui/fabric8-recommender/pull/447
Problem
In the
http://openshift.io/<space_name>
page you get to create a work item. Once you click on the button it takes you to a page where you get to select a work item type. Once you select a type it takes you to a page where you can create a new work item of that selected type. This flow is currently broken (https://github.com/openshiftio/openshift.io/issues/2741), but before we fix it, let's revisit.Why is this broken?
Now planner does not allow non-contextual adding of a work item. The user has to follow the guided type inside planner.
Possible solution
I heard there is a solution approach being discussed to have a special work item type for creating non-contextual work items or issue, but for now, we can disable creating work item anywhere outside of the planner.