Skip to main content
All CollectionsManaging Your Workflow
Customize Your Team's Workflow
Customize Your Team's Workflow
Toshi Dávila avatar
Written by Toshi Dávila
Updated over 2 weeks ago

Assembla’s system is flexible enough to meet the needs of almost any team or project. In order to get the most out of your Assembla projects, here are some tips and tricks to help you and your team work smarter and faster.

Adding custom status workflows to match your process

If you want to change the name of an existing column, simply double click the name of the column.

You can also create new statuses and rearrange their order by going to Tickets Settings > Status and Workflow. Use this page to adjust the order of the statuses in the drop-down field on tickets and the order of the columns from left to right on your Cardwall view.

Creating custom ticket fields for more detailed ticket requirements

You can create custom ticket fields to add more detail to your tickets. For example, add “Due Date” using the date custom type or “Tester” using the team list custom type.

Go to Tickets Settings > Ticket Fields. You can create new custom fields, rearrange the order of custom ticket fields, set required custom fields, and define default values for ticket fields. When setting new custom fields, you can choose between text, numeric, list, team list, date, date/time, and checkbox options.

Using Assembla’s markup language to quickly reference tickets, commits, files, embed images inline, and more

You can use the markup language shortcuts by directly typing the syntax into any text area or by using the toolbar above the text areas. Shortcuts include:

  • Reference another ticket by typing in #ticket_number such as #112.

  • Link to a file with [[file:file_name]] such as [[file:screenshot.png]].

  • Directly embed an image inline with [[image:file_name]] such as [[image:screenshot.png]].

Changing the default Tickets view to what is most important to you

You can change the default Tickets view so that when team members visit the tool, they immediately land on the view that is most important to you, whether List, Planner, or Cardwall.

Go to Tickets Settings > Default Views, and then select the desired default view.

Creating an Epic or Story helps manage ticket relationships

You can create larger "parent" tickets as an Epic or Story to manage ticket relationships. These relationships help you break up bigger tasks into smaller, more manageable chunks.

When creating a new ticket, select Epic or Story from the plan level dropdown. When you create an epic, the Related Tickets section includes a link to Add new child story. When you create a new story, the Related Tickets section includes a link to Add new subtask. You can also add and modify relationships from any ticket via the Related Tickets subtab.

Building team filters to get the desired list of tickets for your team

Visit the ticket List view and click on the Filters option. Build the desired filter, and click Save filters. Provide a descriptive name, check Visible for the team, and click Save as new. Now visit the Ticket Settings > Default Views section, and select Land on Ticket List.

Using time estimates

If your team uses time estimates, you can enable estimates and choose between different types:

  • time (hours)

  • points

  • size (small/medium/large)

Go to Tickets Settings > Ticket Fields, and select the desired Estimation from the available list. You can also disable estimates from this section.

Identifying “stuck” tickets

"Stuck" tickets are tickets that the status has not changed for a defined period of time. Sometimes these tickets are either not important (you can move to another milestone), are forgotten, or need some assistance.

Go to Metrics > Stuck Tickets. Define the amount of time you consider "stuck," and see a report of those tickets.

Viewing the status of stories in progress

You can get a quick view of stories in progress by going to Metrics > Stories Lifecycle. Here you will see a list of all stories, the number of active tickets, a progress report, and the story owner. Click on any story to open it up and see more details.

Importing tickets from Jira and other tools into Assembla

You can import tickets into Assembla from another tool such as Jira. Go to Tickets Settings > Export & Import. Select the type of file you want to import, and then browse for your file. After selecting your file, click Import Tickets.

Need help? Please contact us at support@assembla.com.

Did this answer your question?