Asana - Best Practices

This guide is supposed to tell you about the current best practices while using Asana as the INSPIRE tracker.

  • When writing a new task...
    • keep the title short and concise. e.g. "LaTeX CV format problem" instead of "There is a problem with LaTeX CV format when searching for bla bla".
    • add a description of the problem in "notes" in the detailed task pane
    • add appropriate type tag (#bug, #feature or #chore) Read more about tags below
    • add related projects when applicable
    • add followers to this task (for example, a new task in BibEdit it is good to add Javier as follower)
  • Use subtasks when applicable - when bigger tasks can be broken down into individual tasks.
  • Use you inbox to stay updated in tasks/projects you follow (just below "My tasks" in the top-left corner)
  • Tip: to link within Asana to other tasks, projects or persons - start typing @ and you get an autosuggested list to choose from.

Using tags

We have defined some standard tags to be used when creating a new task and updating it. Tags are added by clicking on "tags" when looking at the detailed task pane. Just start writing the tag you want to give and it will auto-suggest a tagname for you if it already exists. Tags should always be lower case.

Type tags

When creating a new task it is highly recommended to add an appropriate tag indicating the type of the task:

  • #bug - used when reporting a bug in INSPIRE
  • #feature - used when creating a task to develop a new feature
  • #chore - used to indicate tasks that can be designated a "chore" e.g. moving all DOIs from tag X to tag Y

Status tags

Sometimes a task is in a certain state that is useful to convey quickly. For example, a task is in testing or waiting to be deployed.

  • @review - task is ready for review - re-assign the task it to the reviewer and add comments to indicate location of branch to review.
  • @testing - task is ready for testing
  • @deploy - task is ready for deployment on production servers
  • @blocked - task is somehow blocked. State reason as a comment.

Other tags

For all other purposes, you can add tags to describe the task and make it easier to filter. For example, for tasks related to certain Invenio modules: bibindex, bibupload

Projects

We define seperate Projects to group tasks that are related to a common topic. Our Asana instance already have some project defined, but as more tasks are added other projects may be added on demand. However, please do not add projects without a good reason - when a certain group of tasks are emerging inside another project and deserves its own. Otherwise it may get messy in the project list.

Priority heading

To define the priority of a task in a project, we will add Priority headings to each project. (These headings can be created by writing a task as usual but in the title finish it with a comma (:).)

The current priorities defined are:

  • Crucial
  • Major
  • Minor
Edit | Attach | Watch | Print version | History: r6 | r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r2 - 2013-01-22 - JanLavik
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Inspire All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback