Root > Solving bugs in your code > Managing bug reports in issue tracker > Bug trackers setup > YouTrack setup

YouTrack setup

Previous pageReturn to chapter overviewNext page   

This article is part of Managing bug report in issue tracker series.


See managing bug reports in issue tracker for common information. Please, read it first. For common information and setup of YouTrack itself - please see this article. The text below assumes that you already completed YouTrack installation.


Below are detailed steps for recommended YouTrack setup for automatic bug report submission. Before going through setup - make sure to upgrade your YouTrack to the latest version.


Some steps below are optional, some steps must be executed only once (like custom fields creation), other are executed from time to time (like creating new projects for your new products) and the rest are executed regularly (like creating product versions).


Full list of necessary actions contains:

1. Creating custom fields (single act)
2. Creating user accounts (single act or per product)
3. Creating projects and setting it up (single act or per product)
4. EurekaLog setup (per product)
5. Testing (as required)
6. Maintaining project (regularly or from time to time)


Please note that all actions below are just examples. It's recommendation, but it's not necessary to be absolutely like that. You may use another configuration.


Note: You can use YouTrack as external bug tracker for GitLab.



Creating custom fields

1. (Settings/Custom Fields)



Create custom field to improve usefulness of EurekaLog. Most important field is "Count" - to store number of sent/occurred problems. Its type should be "Integer"; field name can be arbitrary, like "Occurrences", "Bug count", "Popularity", "Incidents", "Hit Count", etc. Other suggested custom fields are: "BugID" (to store BugID and search issues) and "e-mail" ("user e-mail", which is typically entered in MS Classic error dialog). Both fields should be text fields. Again, field names can be anything.


We strongly recommend to create at least "Count" and "BugID" fields.



Example: three new custom fields


2. Create any other additional fields as you need/like (you can submit values for custom fields at run-time via OnCustomWebFieldsRequest event).


Important: Do not forget to add custom fields to project later.



Creating user accounts

1. (Settings/Users) Create new non-admin user account for bug report submission:



Creating new user


2. Log off, and log in as newly created user. Go to your profile, switch to "Notifications" tab and disable all notifications:



Disabling notifications


3. Create an access token for EurekaLog. Go to "General" tab and click on "Update personal information and manage logins" link:




Go to auth settings


Add a new token. You can name it anything you like.



Creating a new access token for EurekaLog


Once token is created - copy and save it for later (see EurekaLog setup below):



Token created


Log off, and log in back as administrator.


4. Repeat these steps for each bug submitter user account which you want to create.


5. (Optional) You can also create a new group and/or role and include all bug-reporting user accounts into that group (Settings/Groups and Settings/Roles):



Creating new user group for bug reporting



Creating new role for bug reporting


6. (Optional) Open bug reporting group and include bug reporting accounts into it:



Adding bug report accounts to the group


Repeat this for all bug reporting accounts.


7. (Optional) Open bug reporting role and add necessary permissions:



Adding permissions for the role


We recommend to enable the following permissions:

Read project basic
Read project full
Read self
Read user basic
Create issue
Read issue
Update issue
oIssue attachment
Add attachment
oIssue comment
Read comment
oUser profile
Read not own profile


You may select less permissions, if your usage case is not using all features. You may also optionally add permissions for private fields.



Creating projects

1. (Projects) Create project for your software product. You may create several projects - one for each of your software products.



Creating new project for bug reports


2. (Optional) Create components (sub systems) for the projects. Typically component/sybsystem is used for identification of the part of your software product.



Creating component(s) for the project


If you are going to use sybsystems/components in your project - we recommend to make "Subsystem" field public:



Making private "Subsystem" field public


3. Create versions for the project. If you don't use versioning (highly unrecommended) - you can skip this step.


You should create new version for each release of your software. I.e. when you release (publish on site, send to custom, etc) "YourSoftware" - you need to create "" version. When you release update: "YourSoftware" - you need to add "" version.


Version strings can be arbitrary like "1", "1.0", "1.0.1", "" or even " beta 3". However, it's recommended to use four-number versions with optional textual description, for example: "" and " beta 3".


Note: if you don't want to edit project each time you release new version - you can create versions for the future use. I.e. when you release "YourSoftware" - you can create "", "", "", ""..."" versions.


For example:



Opening versions editor



Adding a new version



Releasing or archiving a version


When reporting - version are taken from file's version information, so you must supply the corresponding version in description of your .exe or .dll files.


Note: EurekaLog will use closest match.


Important Note: EurekaLog will not look for "Archived" versions. EurekaLog will only for "Released" versions, if a corresponding option is enabled. Be sure to mark versions of your compiled .exe as "Released" in YouTrack.


4. Add custom fields to the project:




Adding global custom fields to the project


Please note, that custom fields were created earlier (see above). We just adding already existing custom fields to the project.


5. Setup project access rights: permissions and roles.



Adding access to the project


You can specify role and group created earlier, or use standard role and specific user accounts.



Enabling external access to bug tracker

1. (Settings/Global Settings) Enable access to bug tracker via API calls:



Enable "Allow all origins" option

or set up individual origins (for corporate environment)


Please, refer to YouTrack documentation for more information.



EurekaLog setup

1. Enter YouTrack details into EurekaLog settings of your projects:



YouTrack settings filled into EurekaLog options


Important Note: use API token created earlier. After you have entered token into EurekaLog's settings - delete token from whatever place it was saved (clipboard, text file, etc.).


If you forgot your token, you will have to delete it, and create a new token.


2. Set any additional/common send options.


3. Set/fill custom fields. EurekaLog has support for automatic managing of "Count", "BugID" and "E-Mail" fields. You just need to enter field names in EurekaLog options. For other custom fields you have to fill them manually, for example:



  EEvents, ESysInfo;


procedure SetCustomFields(const ACustom: Pointer; AExceptionInfo: TEurekaExceptionInfo; 

  ASender: TObject; AWebFields: TStrings; var ACallNextHandler: Boolean);


  AWebFields.Values['License'] := GetYourApplicationLicense;




  RegisterEventCustomWebFieldsRequest(nil, SetCustomFields);



4. Add any custom data, additional attached files, write necessary event handlers, set exception filters, etc, etc.




1. Test sending. You can do this right in the EurekaLog send options dialog - by clicking on "Test..." button. This will send test bug report.


Suggested actions are:

1. Click on "Test..." button to test sending and creating of a new bug issue in YouTrack.
2. Resolve any found issues (access denied, wrong values in fields, etc).
3. Once successful and there is new issue in YouTrack - click on "Test..." button again. This should test updating project.
4. Resolve any found issues (access denied, etc).
5. Once successful - close existing test issue in YouTrack (as "Fixed"). Optionally - add a comment with special tags (see customizing feedback).
6. Click on "Test..." button again. This should test sending old (already fixed) bugs (see: issues workflow).
7. Ensure there is no error messages, no problems. You should get "success, this bug is fixed" kind of behaviour. Exact behaviour depends on your settings.
8. Delete test issue in YouTrack after testing.


These actions should test that sending is actually working.


2. Now it's time to test your application-specific sending.


1. Place debug code in your application to raise a test exception and cause a test leak (if you've enabled leaks collecting).
2. Run your application and invoke this test code.
3. Let application crash and process bug (show dialog, send bug report, etc).
4. Ensure that behaviour is expected.
5. Ensure that you get all files and additional information in YouTrack.
6. Remove test code from your application.


Now your application is ready for deployment.



Maintaining projects

1. You need to create or update project versions when you ship new release of your software. If you've created a batch of versions in YouTrack for future use - you may skip it until you've run out of versions.



See also:

Send feedback... Build date: 2022-03-28
Last edited: 2022-01-14
The documentation team uses the feedback submitted to improve the EurekaLog documentation. We do not use your e-mail address for any other purpose. We will remove your e-mail address from our system after the issue you are reporting has been resolved. While we are working to resolve this issue, we may send you an e-mail message to request more information about your feedback. After the issues have been addressed, we may send you an email message to let you know that your feedback has been addressed.

Permanent link to this article: