-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mapping mockups to user stories #47
Comments
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. 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....) |
@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: |
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 think I would want to see my unfinished processes as the default, and finishe processes separately (as history). |
Let's recap...
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? |
👍 |
I think more permissions: either creator of the process or superuser?
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?
Meaning a commitment that you created, right? (or superuser)
finished/unfinished |
Are permissions already working on the backend?
both?
yes! |
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. |
one or the other |
Not sure the best way to do this, but trying it as a new issue, so it is a snapshot in one place.
Question: What is "Taxonomy" button for?
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.
The text was updated successfully, but these errors were encountered: