🏷️Properties

Properties bring structure to your data in Cycle. Whether you’re triaging feedback, categorizing quotes, or segmenting requests, properties help you slice and dice information based on what matters most to your team.

Built-in & Custom Properties

Every doc type — Feedback, Quote, and Request — comes with built-in properties to help you get started:

• Reporter: Who submitted it

• Source: Where it came from (e.g. Slack, Intercom)

• Status: Lifecycle stage (e.g. “To Process”, “Processing”, “Processed”)

But you don’t have to stop there. You can create custom properties that reflect your unique workflows.

---

🔧 Create a Custom Property

Custom properties let you tailor your workspace. For example: mark urgency levels, indicate platforms affected, or assign a responsible team.

Here’s how to create one:

1. Go to your Workspace Settings → Properties.

2. Scroll to the bottom and click Add new.

3. Give your property:

   • A name (e.g., “Urgency”)

   • A field type (Single select, Multi-select, Checkbox, Date picker, URL, etc.)

   • A color (optional)

4. Click Save.

5. Choose which Doc Types this property applies to: Feedback, Quote, Request—or all three.

6. Optionally, filter even deeper:

   • Link the property to specific Request types (e.g. only show Affected Platforms for “Problems”, not “Feature Requests”).

Here's a short video guide showing how to create a Affected Platforms property 👇

---

💡 Property Suggestions

Here’s what our power users often create. Use them as inspiration:

Property	Type	Use Case
Priority / Importance	Single select	Triage feedback by urgency
Complexity / Effort	Single select	Evaluate implementation difficulty
Impact	Single select	Estimate user or business impact
Time Horizon	Single select	Classify by urgency: Now, Soon, Later
Sprint	Date picker	Track in which sprint it was addressed
Internal Resource	URL	Link to spec, design, or issue tracker

---

🌀 Property Inheritance

Cycle supports top-down inheritance for properties that are shared between doc types. This keeps related data aligned across Feedback, Quotes, and Requests.

Default chain:

Feedback → Quote → Request

Here’s how it works:

• If a property is shared, it flows down:

  • Updating a Feedback’s Urgency updates the linked Quotes and Request Urgency.

• If a child doc already has a value, it won’t be overwritten—unless it’s an Quote, which always inherits.

• If a property isn’t shared, it won’t be inherited at all.

Example:

• “Urgency” is shared across Feedback, Quotes, and Requests → inheritance works.

• “Effort” is only used in Requests → Quotes won’t inherit it.

---

Properties help your team bring order to chaos. Structure your data without stripping away context—and power up your views, filters, and workflows.