I deleted the existing stages in Odoo project and created three stages:
Todo
Doing
Done
How to ensure that the tasks moved to "Done" are assumed as complete (ie. they are no longer highlighted with RED after assigned deadline)?
I tried enabling the Debug view and "Edit Workflow" from the Projects page. The workflow is empty. There is an option to "Import" a csv file. Is there a way to generate this CSV?
Update1:
Based on this bug/explanation , I think I have deleted the stages. (extract below)
Bug Description
This is a usability issue:
After creating a new project, A Project Manager clicks on it project
at the Project Kanban view and navigates to the Task Kanban View.
There he deletes one of the Stage, to remove it from it's project
stage list. However, this actually deletes the Stage from the Stages
table, so it's also removed from all other projects.
My suggestion is to remove the Stages "delete" option at Kanban Views:
this should be done only on the Project's definitions Stage list.
Is it possible to restore the original stages so that I can use the stage "Completed" for marking tasks as complete?
Mark the stage "Done" as a 'folded' state.
The original stage definitions are contained in the file addons/project/project_data.xml and marked as no_update=='1' so that they will not be recreated upon updating the project module.
There are three 'folded' stage definitions, which you can refer to with the external IDs project.project_tt_merge, project.project_tt_deployment (labeled 'Done'), and project.project_tt_cancel.
These are suggestions only and can certainly be deleted and replaced with your own definitions.
Configure the "Done" activity with the "flow_stop" attribute set to True. That is the way a workflow instance is considered completed.
Info: https://www.odoo.com/documentation/8.0/reference/workflows.html
Related
I have a azure boards project with simple flow.
We only use Epics / Issues, almost never work-items for sake of simplicity.
Can I customize the Sprint Taskboard (or create new board), so that it will show Issues in the state columns instead workitems?
You can customize the Product backlog Board to do exactly what you want. In which case you could completely ignore the "Sprints":
If needed add additional columns:
To end up with something like this:
You may create a child process based on Agile: Create and manage inherited processes and assign your project to it.
After that, you may assign Issue to any backlog level... as example:
open the task backlog level:
Add issue to the task level:
Use it in the sprint:
I have a reasonably complex release pipeline in Azure DevOps that releases a number of Azure apps, a database etc.
Each step is genericised using a library variable for the environment. For example:
But library variables are linked to a release or a selection of stages.
Currently I have to clone the entire pipeline and link a new library variable group in the clone to publish a different environment, but this is heavy on unwanted duplication and maintenance.
How can I run the same release pipeline with different library variables?
If I could do this, it would be possible to have a release for a given branch, for example, but I cannot see a way to do it.
At of this time, it is not supported to select which variable groups to use when you create a release.
If you only have one or several variables, I think you can use pipeline variables instead of variable groups, so that you can update them at release time. Here are the detailed steps:
Go to your pipeline editing page and select "Variables" tab. Click "Add" to add a variable. Then check the option "Settable at release time".
Try re-create your release. You will find the variables defined in #1 and you can edit them before create the release.
If you have many variables, I suggest you try to change the structure of your pipeline to make it more suitable for deployment to multiple environments. As Daniel said, you can use stages for each environment, and then use the variable group in stages scope.
How can we add calculated custom fields on a process in Azure DevOps Boards. Is there any extensions that can be used for creating a Calculated custom field?
Azure DevOps support rollups in the backlogs only: Display rollup progress or totals.
To use your own logic, you can:
Create an extension (for example WSJF (Weighted Shortest Job First)).
Use az boards work-item to get, calculate, and update fields.
Use Excel to create calculated columns and publish fields: Bulk add or modify work items with Excel
If you mean creating a custom field Calculated to your project process. You can follow below steps.
1, Go to organization settings -->Process-->Select the process which your project is currently using.
If your project is using the System processes: Agile, Basic, Scrum, and CMMI. You need to create Inherited processes. For System processes are locked from being changed. See System versus inherited processes.
After you select your project process. You can select work item types to add the custom field. See Add a custom field.
2, If your project was using System processes. After you created the Inherited process, and added the custom field. You need to change your project process to this newly created inherited process. See Change the project process.
We have 100+ services/apps in a repository in Azure Devops. We have defined a single CI/CD YAML multistage pipeline for each (build and deployment). This limits blast radius and allows for auditability of each release of each project. We rely on templates for all the real pipeline work so this is easy to maintain; just a small root azure-pipelines.yml file for each project that includes the needed templates.
Now, we'd like to start using PR validation builds. And, as best as I can tell, we have two options:
Create a separate PR build for for every project and use the UI/API for policies to create 100+ policies
Create a single PR build that has stages for all 100+ projects.
I'm not a fan of the 1st option as now we'll have 200+ builds. The 2nd option is possible, but to avoid a 3 hour PR build, we'd need a way to only run needed stages (aka project builds).
Is there a 3rd option I'm missing? If the 2nd option is our best bet, how do we turn off stages for projects not changed in that PR (i.e. what condition would we use)?
(FYI, our policy is to change only one project per PR, but there are, on occasion exceptions to that.)
For personal suggestion, I also recommend the second method. Though the build script would be very large in one configure file, but much better than have hundreds build configuration files.
But the difficulty is these 100+ apps are all in one repository. This means all the normal method will not suitable for you, include using Build.Repository.Name value as the stage condition. Also, there's no more details which describing the source file path stored in the commit.
So, I suggest you and your team developers input the project name info into your commit message. Then, in the build pipeline you could use the variable Build.SourceVersionMessage to get its comment message. Since this is a environment variable which only work in step level(Not work for stage level and the job level), it needs you add one task in the first step and use the condition for it.
The logic of it is add one step as the first one in every stages. This step is only used to conditional judgment. If the Build.SourceVersionMessage matches the prefix or any key contents words, the jobs will be early-exit.
If use the condition like this:
condition: startsWith(variables['Build.SourceVersionMessage'], '[maven-plugin]')
It needs your commit message must follow a strict content writing format, starting with the specified project name.
Another condition can for you consider is:
condition: in(variables['Build.SourceVersionMessage'], 'maven-plugin')
This does not need the strict content writing format, but also need input the project name in the commit message. Thus it could be evaluated in the job condition with the above script.
Hope it could give you some help.
I have more than 35 projects in an organization in Azure DevOps. These are the solutions of a Single product. Right now I am creating build and release pipelines for each project one by one.
If I create a pipeline for a single project and release the build, I want devops to create pipeline & releases builds for all the other projects(in the same organization) together at once.
For eg, There are projects A,B,C & D. If I create a release pipeline for Project A, will Devops automatically Release build for other projects "B,C & D" in the same organization at the same time.
We need to avoid creating pipelines for each projects one by one. Is this possible and is there any scripting or configuration to achieve this?
Thanks in Advance.
The process of setting up multiple release definitions with the exact same tasks can be very time consuming and difficult to manage -- fortunately, our team solved this problem using Task Groups!
Task Groups allow you to bundle multiple steps into a single "group", parameterize them, and then invoke them like a single step. You can also edit the Task Group at any time which will cascade to all places where it's used.
The other consideration is that you can bundle your custom variables into Variable Groups and reuse them between Release Definitions. Having your configuration reusable also has the benefit of only having to edit a single item.
I'd recommend:
Create a single release definition as a golden reference example.
Add your build steps for a single stage/environment
Once you're happy with this release definition, multi-select the steps you want to bundle into a group, open the context menu and select the option to convert to a Task Group. This will remove the steps from your release and move them to the Task Group.
Customize the Task Group with the appropriate parameters and then save it.
Modify your release definition to use the Task group parameters.
Add the additional stages to your environment, and add your custom Task Group to each parameterizing with configuration specific to the environment.
Once you're happy with the Release Definition -- use the Clone feature to create 34 more instances.
The same approach can be applied to builds.