Was this email sent or received by Axosoft.

If you are filtering items by a specific release, do you want to include items belonging to its sub releases?

If you are filtering items by a specific project, do you want to include emails belonging to its sub projects?

If you are filtering items by a specific project, do you want to include items belonging to its sub projects?

This trigger should fire when a project is created under the specified parent or any projects under it.

This trigger should fire when a release is created under the specified parent or any releases under it.

What company does this contact belong to?

Set to 'Approved' if you would like this contact to be able to log in to the Customer Portal immediatley.

If set to 'yes' the contact will automatically be sent an account activation email with login details.

In Axosoft, customers are collections of people grouped by company.

What kind of item should be created (e.g. Feature, Defect, etc.)?

What is the title/name of the item you would like created?

What release you would like to your item to be completed in?

Select this if you are making a sub-item. **Important:** Be sure to select an `Item Type` first!

What person or team doing the work for the item?

Select this if you are making a sub-project.

What is the name of the project you would like created?

This is the key displayed when going to Tools / Other Settings / Source Control Types.

Url a user would go to in order to view changes made in this commit. This url is clickable within the Axosoft suite.

The date and time at which the commit was made. If this isn't received, it will be automatically set to the time at which Axosoft processes the request.

The name or ID used by the user to log in to the source control system. This is what Axosoft will attempt to map to a user (using their Source Control User Name configured in "Tools > People > Users").

The email address for the user. The person configuring the Axosoft Suite to use your integration will have the option to attempt to map any commits without a matching user login to a user by email if one is present.

A human name to show to Axosoft users for who made the commit.

The url a user can navigate to to see the changes made to this file.
.

What was done to the file. You can specify 3 values for this: "added", "removed" and "modified" (case sensitive). Leaving this empty or sending any other value with default the action type in Axosoft to "unspecified".

This is the id used by your source control system to reference the commit.

Source Control Application that's triggering the post. i.e. BitBucket or others.

A field that is tagged with an Axosoft item type and item id. Tags must follow the format

```sh
[axoX: Y]
```
Where Y is the item id and X in axoX can be:

- d for defects (axod)
- f for user stories (features) (axof)
- t for custom items (tasks) (axot)

> Note: d, f, and t are constant even if you've renamed the item types in Axosoft.

In Axosoft, worklogs are tied to items. They must have an item type (e.g. features, defects, etc.) associated with them.

> Mapping this field will take precedence over any values in the tagged item type field.

You must specify an item id to associate the work log to. You can choose and item from the list, key in the item id manually, or use the advanced option to map it to a trigger field.

> Mapping this field will take precedence over any values in the tagged item id field.

The time unit you want to use when saving the work log to Axosoft (e.g. minutes, hours, etc.).

Tell us how many units of the incoming data it takes to equal one unit of the Axosoft time unit you chose to save the work log with. The table below will help you set the value of this field:

<table>
<thead>
<tr><th>Incoming Units</th><th>Work Log Units</th><th>Conversion Value</th></tr>
</thead>
<tbody>
<tr><td>hours</td><td>hours</td><td>1</td></tr>
<tr><td>minutes</td><td>hours</td><td>60</td></tr>
<tr><td>milliseconds</td><td>minutes</td><td>60000</td></tr>
<tr><td>days</td><td>hours</td><td>0.125 (assuming 8 hours = 1 day)</td></tr>
</tbody>
</table>.

Do you want the remaining time to be updated based on the work that was done?

The amount of time remaining for the associated item. (leave blank to auto calculate based on work done).

The Axosoft time unit you want to save the remaining time with.

Tell us how many units of the incoming data it takes to equal one unit of the Axosoft time unit you chose to save the remaining time with. The table below will help you set the value of this field:


<table>
<thead>
<tr><th>Incoming Units</th><th>Remaining Time Units</th><th>Conversion Value</th></tr>
</thead>
<tbody>
<tr><td>hours</td><td>hours</td><td>1</td></tr>
<tr><td>minutes</td><td>hours</td><td>60</td></tr>
<tr><td>milliseconds</td><td>minutes</td><td>60000</td></tr>
<tr><td>days</td><td>hours</td><td>0.125 (assuming 8 hours = 1 day)</td></tr>
</tbody>
</table>.

Axosoft is agile project management for software development teams.

Axosoft

Pivotal Tracker is a collaborative, project management tool for developers and agile product management teams.

Pivotal Tracker

Jira is a bug and issue tracking tool that allows software developers to manage product development and build better software. This integration connects to self-hosted instances of Jira.

Jira Software Server

LiquidPlanner Classic, online project management with predictive scheduling that updates automatically when things change.

LiquidPlanner Classic

Targetprocess is a Visual Management Software.

Zapier Automation Platform

PRODUCTS

CAPABILITIES

By use case

By app

By team

By company size

How Zapier Zaps

How Zapier Uses AI

By team

Learn more

Get help

Zapier quick-start guide

Developer resources

Axosoft Integrations

Axosoft Help & Support

About Axosoft

Related categories

Similar apps

Pivotal Tracker

Jira Software Server

LiquidPlanner Classic