tag:help.lighthouseapp.com,2008-09-20:/discussions/questions/7745-priorityLighthouse: Discussion 2020-02-06T22:40:28Ztag:help.lighthouseapp.com,2008-09-20:Comment/479451672019-12-26T09:55:32Z2019-12-26T09:55:32ZPriority<div><p>What does the mean of priority 9999?<br>
If any document related to priority please send me a link.<br>
Thanks in advance</p></div>amit.lodhi (at avekshaa)tag:help.lighthouseapp.com,2008-09-20:Comment/479451672020-01-13T21:15:00Z2020-01-13T21:15:00ZPriority<div><p>Hi Amit,</p>
<p>Apologies for the delay.</p>
<p>In the past, the <code>priority</code> field used to represent both <code>importance</code> (low/medium/high) and milestone order (the order that you get by using drag and drop on the milestone page). This was a bit of a pain, so we separated those two fields in <code>importance</code> and <code>milestone-order</code>. For compatibility reasons, and to avoid breaking apps relying on the API, we kept <code>priority</code> and its original behavior. So:</p>
<ul>
<li>
<p><code>Importance</code> is read/write from the API, no matter whether you have access to it in the UI or not. This is an oversight, but frankly it's not a big problem. I'll create a ticket to iron out this behavior in the future, but it's a low priority.</p>
</li>
<li>
<p><code>Milestone order</code> is similarly read/write, but it is unusual to use it, as it's really a manual ordering of tickets in a milestone. It is set to 9999 on creation to put new tickets at the bottom of the list, and then you can set it on updates.</p>
</li>
<li>
<p><code>priority</code> is also read/write, and its behavior will depend on whether you have enabled the importance field or not. If it's on, <code>priority == importance</code>, otherwise <code>priority == milestone order</code>. This is a deprecated field and is mostly kept for compatibility reasons.</p>
</li>
</ul>
<p>I hope this answers your question.</p>
<p>Thank you,<br>
Brandi</p></div>brandi