---
title: "FAQs for Technical Debt Tracker in Bitbucket Server"
canonical: "https://support.appfire.com/space/SUPPORT/80880964/FAQs%20for%20Technical%20Debt%20Tracker%20in%20Bitbucket%20Server"
format: markdown
---
## <span style="color: #333333">Overview</span>

<span style="color: #333333">This page presents answers to the most frequently asked questions about the functionality of the Technical Debt Tracker app in Bitbucket Server.</span>

## <span style="color: #333333">FAQ</span>

<details>
<summary>How to visualize the comments?</summary>

<span style="color: #333333">The developers can stay in the code while solving the common problem of tracking technical debt. Upon commit, tech insights scan the repository for the comments like TODO and FIXME and provide a list.</span>
</details>

<details>
<summary>How to allow the users to vote tasks?</summary>

<span style="color: #333333">Crowdsource your prioritization decisions by allowing users to vote the tasks that they want to be completed. This feature is available with a valid license and you can toggle it on or off per repository.</span>
</details>

<details>
<summary>How to create Jira issues for listed tasks?</summary>

<span style="color: #333333">If lightweight task management is not enough, link with Jira to allow users to create Jira issues for listed tasks.</span>
</details>

<details>
<summary>How to create Jira issue?</summary>

1. <span style="color: #333333">Click </span>> Macro (inline-media-image)

<span style="color: #333333"> on the top left corner.</span>
2. <span style="color: #333333">Select the Jira Project, in which the current issue needs to be created.</span>  
> Macro (inline-media-image)
3. <span style="color: #333333">Select a value from the </span>*<span style="color: #333333">Issue Types </span>*<span style="color: #333333">list:</span>  
> Macro (inline-media-image)
4. <span style="color: #333333">Provide the </span>*<span style="color: #333333">Summary</span>*<span style="color: #333333"> and </span>*<span style="color: #333333">Description</span>*<span style="color: #333333">:</span>  
> Macro (inline-media-image)
5. <span style="color: #333333">Click </span>**<span style="color: #333333">Create issue. </span>**<span style="color: #333333">Jira issue is created for you.</span>
</details>

<details>
<summary>What Administrators see if there are no comments or the repository hasn't been scanned?</summary>

<span style="color: #333333">The Administrators can see the </span>**<span style="color: #333333">scan the repository </span>**<span style="color: #333333">button. Scanning the repository can take a long time and be resource-intensive. Non-administrator users cannot see the </span>**<span style="color: #333333">scan the repository</span>**<span style="color: #333333"> button, but rather a message to contact the administrator.</span>

![image]()
</details>

<details>
<summary>Who can use this app?</summary>

<span style="color: #333333">Even though this app is configured by the Administrator, it can also be used by the Developers.</span>
</details>

<details>
<summary>What are the two features that are available with evaluation and commercial license?</summary>

<span style="color: #333333">Allow voting and Create Jira issues are the two features that are available with evaluation and commercial license.</span>
</details>

<details>
<summary>Can Technical Debt Tracker be scanned automatically?</summary>

<span style="color: #333333">The initial scan has to be done manually to find historical items. After that, it's done on each git push.</span>
</details>

<details>
<summary>How to add new labels?</summary>

<span style="color: #333333">Add new labels features is available from 1.5 version onwards. To add a new label to the Standard TODO and FIXME labels by simply going to global administration and supply the labels. Labels are constrained to A-Z and 1-9. No special characters are allowed.</span>
</details>

<details>
<summary>What are the supported formats?</summary>

| <span style="color: #333333">**Parser**</span> | <span style="color: #333333">**Default file extension**</span> | <span style="color: #333333">**Comment format**</span> |
| --- | --- | --- |
| <span style="color: #333333">Markup style</span> | <span style="color: #333333">*.htm</span>  
<span style="color: #333333">*.html</span>  
<span style="color: #333333">*.xml</span>  
<span style="color: #333333">*.php</span> | `<!-- TODO:`<br>`FIXME:`<br>`-->` |
| <span style="color: #333333">Java/C style</span> | <span style="color: #333333">*.js</span>  
<span style="color: #333333">*.java</span>  
<span style="color: #333333">*.as</span>  
<span style="color: #333333">*.cs</span>  
<span style="color: #333333">*.h</span>  
<span style="color: #333333">*.hh</span>  
<span style="color: #333333">*.hpp</span>  
<span style="color: #333333">*.hxx</span>  
<span style="color: #333333">*.h++</span>  
<span style="color: #333333">*.cc</span>  
<span style="color: #333333">*.cpp</span>  
<span style="color: #333333">*.cxx</span>  
<span style="color: #333333">*.c++</span>  
<span style="color: #333333">*.c</span>  
<span style="color: #333333">*.m</span>  
<span style="color: #333333">*.mm</span>  
<span style="color: #333333">*.xib</span>  
<span style="color: #333333">*.php</span>  
<span style="color: #333333">*.css</span>  
<span style="color: #333333">*.scala</span>  
<span style="color: #333333">*.groovy</span> | `// TODO:`<br>`// FIXME:`<br>`/*`<br>`TODO:`<br>`FIXME:`<br>`*/` |
| <span style="color: #333333">Ruby/Perl/Hash style</span> | <span style="color: #333333">*.rb</span>  
<span style="color: #333333">*.pl</span>  
<span style="color: #333333">*.py</span>  
<span style="color: #333333">*.python</span>  
<span style="color: #333333">*.pp</span>  
<span style="color: #333333">*.sh</span>  
<span style="color: #333333">*.yaml</span> | `# TODO: ` |
</details>