Mapping mockups to user stories

[fosterlynn]

Not sure the best way to do this, but trying it as a new issue, so it is a snapshot in one place.

• As a member of a project, I want to see all the details of the project. (this would include planned dates, description, etc.)

Question: What is "Taxonomy" button for?

• As a person, I want to see all the projects I’m subscribed to, by my role. (I think maybe we should just get rid of the "by my role"?) (is this covered here? sort of covered by the dropdown.....)
• As a member of a project, I want to be able to delete a process that has no actual events recorded on it.

• As a member of a project, I want to be able to edit details of the process.
• As a member of a project, I can mark a process finished.
• As a member of a project, I can mark a finished process as unfinished.
• As a member of a project, I want to be able to add requirements of any type in the planned process. (only missing inputs)
• As a member of a project, I can edit a non-work requirement in the planned process.
• As a member of a project, I can delete a non-work requirement of any type in the planned process, if there are no actual events logged against it.
• As a coordinator of a project, I can edit a work requirement in the planned process.
• As a coordinator of a project, I can delete a work requirement of any type in the planned process, if there are no actual events logged against it.
• As a member of a project, I can commit to working on a process task.
• As a member of a project, I can remove my commitment to work on a process task. (?)
• As a member of a project, I can record my work on a planned process task.
• As a member of a project, I can record my work for a process without a planned process task.
• As a member of a project, I can edit my recorded work on a process.
• As a member of a project, I can delete my recorded work on a process.
• As a member of a project, I can join a process task that someone else already committed to, notifying the other person.
• As a member of a project, I can record non-work inputs and outputs (materials, equipment usage, citations, output produced) that have been planned. (this is there for outputs; would be good to show the inputs on the mockup to know where they go)
• As a member of a project, I can record non-work inputs and outputs (materials, equipment usage, citations, output produced) that have not been planned.
• As a member of a project, I can delete non-work inputs and outputs (materials, equipment usage, citations, output produced) that I have created.
• As a member of a project, I can see previous and next processes to the one I am working on, so that I can understand the needs for my outputs and the status of my inputs in the sequence of processes.

These I think would go on other pages:

• As a person, I want to see all the projects I am allowed to subscribe to.

• As a member of a project, I want to see the contribution history related to the project. (could this be a link from the Project page, maybe one of the Overview slots?)

• As a member, I want to see all the tasks of any type (process, simple for now - extra later) I am working on.

• As a member of a project, I want to create new simple tasks.

• As a member, I can edit any simple task that I have created.

• As a member, I can delete any simple task that I have created, if work has not been done on it.

• As a member, I can record my work on a simple task and mark it complete.

• As a member, I can edit any work contributions I have made.

• As a member, I can delete any work contributions I have made.

• As a person, I want to see my contribution history.

• As a member of a project, I want to plan a process from scratch.

[ivanminutillo]

What is "Taxonomy" button for?

Ideally I proposed to insert a taxonomy label (its not a button) to distinguish different processes more easily and to help filter them (so instead of 'taxonomy' think that on each process there is a different word with a different background color that rapresent the specific taxonomy.
The taxonomy could be whatever category we decide, like the categories or tags taxonomy in a blog. In a process what could be the best taxonomy to insert in? Could be usefull or we can avoid it at this moment?

[ivanminutillo]

As a member of a project, I want to be able to delete a process that has no actual events recorded on it.

As a member of a project, I want to be able to edit details of the process.

Hovering on a process it will appear the 'open' button and the three point icon, if you click on the icon it will appear a dropdown with the other actions you can do on the process, one of them is the delete the process and another is 'edit details'
I dont know if it make sense to hidden inside a dropdown this actions or we can display them on hover...
I think it depends on how many actions you can perform on a process other than 'open' 'edit' and 'delete'

[fosterlynn]

In a process what could be the best taxonomy to insert in?

The one that exists now is called ProcessType. It is flat, not hierarchial, and is 1:m with Process. (In ValueFlows there will probably be more of a taxonomy accessible from anywhere, but later for that....)

[bhaugen]

What is "Taxonomy" button for?

Ideally I proposed to insert a taxonomy label (its not a button) to distinguish different processes more easily and to help filter them (so instead of 'taxonomy' think that on each process there is a different word with a different background color that rapresent the specific taxonomy.

The one that exists now is called ProcessType.

@ivanminutillo what did you have in mind for a taxonomy label? The ProcessType might tell you something, but is often duplicated in the process name. But processes have a lot of info you could use for a label: the context_agent tells you which project or other org it's for, it might be part of a work order to make something (we can create a method to tell you that), or we could construct something from some properties, or add something new.

[ivanminutillo]

As a person, I want to see all the projects I am allowed to subscribe to.

[ivanminutillo]

@ivanminutillo what did you have in mind for a taxonomy label? The ProcessType might tell you something, but is often duplicated in the process name. But processes have a lot of info you could use for a label: the context_agent tells you which project or other org it's for, it might be part of a work order to make something (we can create a method to tell you that), or we could construct something from some properties, or add something new.

maybe becouse of we do not have still an urgent need of a "taxonomy" under each process we can use a label to identify the status of a process : finished or unfinished...like this update screenshot:

[ivanminutillo]

I've updated the process page with some missing stories...

[fosterlynn]

maybe becouse of we do not have still an urgent need of a "taxonomy" under each process we can use a label to identify the status of a process : finished or unfinished...like this update screenshot:

I wonder if people will really want to see their finished processes? There has to be some way to get to them, but can it be the exception, not what you generally see on your processes page?

I've updated the process page with some missing stories...

👍

[bhaugen]

I think I would want to see my unfinished processes as the default, and finishe processes separately (as history).

[ivanminutillo]

here a proposal for 'create new process' page. I imagined 3 step to create a new process, in the first step you have to insert the process general information, than in the 2step you have to add new sub-tasks and then in the 3step you have the overview of the unpublished process and if it's all ok you can publish it...
these are the first 2 steps, what do you think about? I've missed something?

[ivanminutillo]

Let's recap...
On this current epic, these are the missing features to implement in order to close it:

• As a user I want to create a new process
• As a user I want to edit a process
• As a user I want to delete a process with no events logged in
• As a user I want to add a planned event on a process
• As a user I want to edit a planned event on a process if no logs was done on it
• As a user I want to log work on a planned event on a process
• As a user I want to log an unplanned event on a process
• As a user I want to delete a personal commitment
• As a user I want to mark a process as finished

I am deliberately avoiding the simple task, as I would like to merge them as "process without an output"... does it make sense for you?

[fosterlynn]

I am deliberately avoiding the simple task, as I would like to merge them as "process without an output"... does it make sense for you?

👍

[fosterlynn]

As a user I want to delete a process with no events logged in

I think more permissions: either creator of the process or superuser?

As a user I want to edit a planned event on a process if no logs was done on it

Should it be OK to edit it even if there are events logged? I think so.

And we need a way to delete events, if you created the event, or superuser?

As a user I want to delete a personal commitment

Meaning a commitment that you created, right? (or superuser)

As a user I want to mark a process as finished

finished/unfinished

[ivanminutillo]

I think more permissions: either creator of the process or superuser?

Are permissions already working on the backend?

Should it be OK to edit it even if there are events logged? I think so.
And we need a way to delete events, if you created the event, or superuser?

both?

Meaning a commitment that you created, right? (or superuser)

yes!

[fosterlynn]

Are permissions already working on the backend?

Nope, gotta do that!! @pospi seemed to think the backend shouldn't tell the UI about the permissions / authorization, but to me it makes sense to encapsulate that on the backend so other UIs would follow the same rules and not have to re-code that logic. What do you think @ivanminutillo @bhaugen others? Is there a standard practice for this? (In OCP, the logic is repeated in the UI and the backend.)

The backend could include permissions in query results related to the user. Would need some standard way to do it.

[fosterlynn]

And we need a way to delete events, if you created the event, or superuser?

both?

one or the other