Rules work in company-managed projects and, with some limits, in team-managed projects.
What works there
| Kind | In team-managed projects |
|---|---|
| Conditions | Only at certain times. |
| Validators | Matches a format, Compare dates, Must change or stay, Checklist done. |
| Post-functions | Clear fields, Set field value, Copy fields, Transition issue, Create work items, Add one to a number, Post a comment, Connect matching work items, Log work, Set field from user property, Back to previous status, Remove matching links, Save a property, Delete, Display message to user, Add or remove labels, Add or remove components. |
Not offered there, and why
- Email issue, Assign and Add or remove watchers read group and role members as the app.
- Copy comments reads comments as the app. Set who can see the work item: team-managed projects have no security levels.
- Sequence of post-functions and Shared action: their steps would skip the run-as check. They also refuse to run on a team-managed project if reached another way, and change nothing.
- Limit how many: its search runs as the app, which could be used to look into other projects.
- The remaining conditions and validators are for company-managed projects only.
Run as in team-managed projects
A post-function there runs only as the person who made the move. If a rule is set to anything else, the run is refused, nothing changes, and run history says to set it to run as the current user. When you edit a workflow from a project’s own settings, the screen offers only that choice.
Copying rules to a team-managed workflow copies only the condition and validators listed above. See Copy, export and apply.
Related pages
Need help with Simple Workflow Automation? Contact us