/
Shortcuts: "t:" searches only in tasks, "p:" searches only in projects, "u:" searches only in users. For example, "t:analysis" or "p:prototypeXYZ" All available shortcuts: t|task|tasks|i|issue|issues - search only by tasks; p|project|projects - search only by projects; u|user|users - search only by users.
Hash #: By using # with task ID, you will jump to the task directly. Without the # symbol, the result only matches the searched numbers (don't expect ID).
Operators AND OR NOT XOR: For example 'man OR (dog AND cat)'.
Operators '+' and '-': A group of terms with some marked with + and - will match items containing all of the + terms, but none of the - terms. Terms not marked with + or - contribute towards the item rankings. You can also use + and - on phrases and on bracketed expressions. For example 'one +two -three'.
Operator NEAR: 'one NEAR two NEAR three' matches items containing those words within 10 words of each other. You can set the threshold to n by using NEAR/n like so: one NEAR/6 two.
Operator ADJ: ADJ is like NEAR but only matches if the words appear in the same order as in the query. So 'one ADJ two ADJ three' matches items containing those three words in that order and within 10 words of each other. You can set the threshold to n by using ADJ/n like so: 'one ADJ/6 two'.
Phrase searches: A phrase surrounded with double quotes ("") matches items containing that exact phrase. Hyphenated words are also treated as phrases, as are cases such as filenames and email addresses (e.g. /etc/passwd or president@whitehouse.gov).
Searching for proper names: If a query term is entered with a capitalised first letter, then it will be searched for unstemmed.
Wildcards: The query parser supports using a trailing '*' wildcard, which matches any number of trailing characters, so 'wildc*'' would match wildcard, wildcarded, wildcards, wildcat, wildcats, etc.
Searching within a free-text field: You can search within specific fields. For example 'title:support content:shop' might find items with 'support' in the title and 'shop' in the content. You can also specify a prefix on a quoted phrase (e.g. title:"one two") or on a bracketed subexpression (e.g. title:(mice men)). Allowed search fields: title, content, journals, attachments.
Recently viewed
Mail subject
Reply to
Mail copy
Mail sender
Mail recipient
<div class="journal-details-container"> <h4> Task #976 has been updated by Asa Wresros. </h4> <div id="journal-5111-notes" class="note"><p>Hi,</p><ol> <li>The text in the OUT-rows is correct (and the IN-rows should be corrected).</li> <li>Thank you. My mistake, I missed to write that it was new plus codes.</li> <li>Thank you, it should be “Inactivated at 31.12.2025”.</li> <li>It is ok to give XU060 and XU061 OR 0 value, and your mapping is ok.</li> <li>Thank you, it sounds good.</li> <li>We think that there is a small, but significant, difference between AK117/KEDE1B (rectal) and AK046/AK118/KEDE1A (percutaneous). A percutaneous investigation is very simple while a rectal investigation is a little more demanding so that is why we want OR 2 and PROCPR 40V14 for AK117/KEDE1B, but not for AK046/AK118/KEDE1A.</li> <li>We think that these procedures can be performed at a follow-up visit, therefore we don't think PROCPR 40V78 is needed here. <span>(As far as we can see in “2024-10-25_Combined2025PR1_xls.xlsx” the plus code PHXX90 does not have PROCPR 40V78).</span> </li> <li>The PROCPRs mentioned above refer to the plus code PJXX05 (Needle biopsy of lymph node) which were our initially mapping suggestion for TPJ30. Later we changed the mapping suggestion to PJXX10 (Puncture of lymphocele) and as far as we can see in “2024-10-25_Combined2025PR1_xls.xlsx” this plus code has only OR 2 and no PROCPRs (except for 05O23 in ice version).</li> </ol></div></div> <hr/> <p>The updates for NCSP, ICD and ATC for SWE2026PR0 can be found in two TCs as indicated by respective names. </p>
