This post is also available in: Français (French)
Topic properties are fields that allow to describe important elements of a topic in a clear and formal way. All properties are optional, but understanding them allows a much more powerful way of dealing with topics.
### Why do I need to set topic property?
You have a topic on a project that needs to be finished by the 15th of December, and which should be worked on by John Doe.
You could of course describe in the text of the topic description, when the topic should be finished and who needs to work on it. But by settings topic properties:
* deadline: 15/12/2017
* assigned person: John Doe
You can set this information and make it available for your whole team in a more formal and readable way.
It also allows to set handy automation that is a much more powerful way of dealing with topics.
When you set the deadline to “15/12/2017”, we will send an email to the assigned person to remind him that the deadline is getting closer. We will show those topics in a distinct way to make them more visible.
Also when you assign a person to a topic, he will be notified. If you have no time to see them anytime soon, they will at least be notified of the work to be done and not waste time on other priorities!
### Which properties can be set?
* Deadline: Deadline is the expected date when the topic should be finished.
* Assigned user: This property allows to assign a topic to one user invited to work on the project. You also could assign yourself, of course!
* Milestone: Milestone is an important date in a project such as a meeting, a competition deadline, etc. You could set this date using deadlines, but if you have more topics that share the same deadline, it is easier and handier to set a milestone. Indeed, if the date changes, you do not need to update all topics, but only the milestone deadline. Also you could filter the topics by a specific deadline in the topic list view.
* Stage: Stage is a broader step of project development commonly used in architecture projects. Usually, architecture projects are broken down into sketch, preliminary design, design and site work. Defining a stage, which a topic belongs to, allows you, for example, to archive all topics of a past stage or access topics that are planned for a future stage in a separate view.
* Priority: Prioritizing urgent over less important things is the key to survive in a busy and stressful workflow of project development. Urgent topics will be highlighted to remind people in your team to handle them first.
* Lot: Lot is a common way to split the work that needs to be done by construction types: walls, facades, interior finishing are possible values of a lot. Depending on the projects you could split them into very specific lots or use only generic separation. Lot is a way to prepare site work and give access to external uses. For example, the construction company can have access only to the topics that are about their specific lot.
I hope you find the topic properties useful. You are not obliged to use all of them. Just test those that are useful for you.