User information
 Loading ...
Show article in Knowledge Base

 Viewing a single issue Export knowledge base Export     SubscribeSubscribe      Show article info

Issue view


This view shows all information about a single issue. You will come to this view after clicking on an issue in the Issues list in the project, or clicking on a search result.


The main parts of the issue view are highlighted in the figure below. The view is made up of several sections where 3-8 also can appear as tabs underneath the details of the issue (2):


issue page

1. Quick function links: This row contains links for useful functions.

  • Print view/Edit view - Shows all the issue information in a printer friendly format/The view where you can edit the issue. It changes from Print to Edit view automatically if you click on the issue when you are in Print view.
  • Direct link - Direct link to the issue
  • Spam - You can tag irrelevant mail generated issues as spam, and they go to the spam folder
  • Send email/Email reply - lets you write an email to the person who last replied or created the issue. Part of the email ticket system.
  • Transfer/Copy - lets you either move the issue to another project, or create a copy of the issue in another project.
  • Merge - lets you merge this issue together with another issue so that two ticket become one.
  • Delete - deletes the issue. Use this with care!
  • Save - Saves any changes to the issue made in this view.


2. Issue details: An issue has a number of fields available. Most of these are completely customizable, so do not worry if your issue view looks a little different! The exact details also depends on issue type - some details are only available in certain issue types. Here is a description of the most common fields.

  • Issue Key - This is a unique key (identifier) assigned to all isssues, in the form of prefix-number, like "Order-3" in this example. This is shown in the title bar. It cannot be changed by the user.
  • Title - The name of the issue. This is a required field, that must be filled. Good names are descriptive and tells something about the issue.
  • Description - A place to describe the issue in detail. This should be as complete as possible, describing everything needed to resolve the task/feature/bug/requirement/etc (depending on what kind of issue this is). The HTML content editor expands when this textarea has focus (In the sample image, its the Comment field that has focus, but not the Desription field).
  • Type - This tells you what type of issue this is. Common types are tasks, bugs, feature requests, requirements and support issues. New types can be created, and which issue types are available also depends on the project settings/customizations.
  • Status - The current status for the issue. The number and names of statuses are customisable, as are notification and workflow rules dependent on issue status changes. Changes in status are one of the main ways to track and manage issues in a project.
  • Severity - Used to indicate the impact and severity/risk of the issue, particularly regarding bugs in software. (not shown in the figure)
  • Priority - Used by to prioritize work, so work is done on the most important things first.
  • Tags - This is a list of tags on the issue, which is used to categorize issues on a glance.
  • Progress - This is a graphic of a small progress bar, showing how work progresses on the issue. It corresponds to Actual time vs Estimated time.
  • Creator - Which user created the issue.
  • Owner - The user that currently is responsible for the issue. Workflow rules can transfer ownership of an issue automatically, on changes in status. Like for example,  transfering an issue back to the reporter for testing after work has been done on it.
  • Developer - Which developer is doing work on an issue. (In the figure, the terminology is changed to Responsible user, but you can change that through Terminology options.)
  • Reporter - Who reported the issue. Usually the person who reported an error, or demanded a new feature. (not shown in the figure)
  • Sprint - You can assign an issue to a sprint of an application. This is the sprint for which the issue should be completed. (This field was earlier named 'Fix for sprint', and may do so in legacy projects.)
  • Affected sprint - If an issue affects a particular sprint, it is shown here. Mostly useful when working with different sprints of software or hardware. (not shown in the figure)
  • Estimated time - The projected time needed to do work on an issue.
  • Actual time - The actual amount of work done on an issue.
  • Remaining time - How much time is needed to finish work on the issue.
  • Due Date - if the issue must be finished by a certain date . (Customized to Deadline in the image)
  • Component - Tells which aspect, or part of a project the issue covers
  • Ticket id - A unique number that is used by the ticket system. (not shown in the figure)

    • Publish external - A flag indicating if the issue is available to users with the role "External", or not. (not shown in the figure)

    • Last replied by - Who last replied to the issue. Mostly used for support issues.

    • Reporter Company - If a user is assigned to a company, the company name is shown. This is helpful if you want to separate issues from different companies

    • Billing amount - This is the amount of money billed on the issue - what you can get paid for

    • Cost amount - This is the internal cost of the issue, like developer salary, etc.

    • Fixed price - If the issue has a fixed price, this is the field for it.

    • Fixed time- If the issue is set to a fixed amount of time to complete, this is where you enter it.

    • Start Date - This can be used in conjunction with Due date for Gantt chart views, for example

    • Add comment - Comments are a way to keep correspondence regarding an issue, on the issue itself, so it is readily available in the issue history. You can set different access permissions on comments, to make sure that only the target user group will see the comment. The HTML content editor expands when this textarea has focus (In the sample image, its the Comment field that has focus, but not the Desription field).

    • Customizable issue fields - Many different issue fields are possible, between those available as defaults, and new custom creations. Which ones you will see for an issue, depends on the exact customization of your project (What issues are in the issue field configuration for the project). Your project may only use a small subset of fields mentioned above, or use all of them plus extra custom fields.


      Sub-tabs or sub-sections: These are either shown as separate sections below each other, or collapsed into a tab area with a number of sub-tabs.

      You can control which view you use by editing your User profile.  Go to the Settings tab, and check the setting Use tabs in "Edit issue" in the Issue settings section.






issue page tabs

3. Sub issues: Issues can have a parent-child relationship, and this area shows the current sub-issues for the main issue in question.

The sub-issues exist as issues in their own right, just that they are linked to the main issue.  A typical example can be breaking up a big task into smaller tasks, and modeling that by having sub-issues off the main task. You can see work progress for the entire group of sub-issues, as well as changing their order, create new sub-issues etc. You can even disconnect a sub-issue from the main issue (it continues to be an issue in its own right)-. Click on any of the sub-issues to go to that issue.


4. Attachments: You can attach files to issues. Here you can see all attachments to the issue, with short descriptions of their content.

You can open attachments, edit descriptions, attach more files to the issue.


5. Links: Here you can see links between issues.

This is useful when an issue is dependent on another issue in some way, and it is not a parent-child relationship. You can go to the linked issue by clicking on it.


6. Work Logs: This is a list showing work done on the issue, and by whom, in the form of Issue work logs.

The list shows the sum of time working on the issue. You can edit and delete worklogs to reflect actual time worked on the issue.


6.1. Expenses: This is a list of expenses related to the issue. Each expense will show the cost, the dated added and who added it to the issue. The sum of expenses on the issue is also shown. You can edit and delete expenses to reflect actual costs on the issue.  This is not shown in the screenshot.


6.2. KB Links: This lists all links to KB articles from this issue. You can click on a link to open the linked article in the KB.  This is not shown in the screenshot.


6.3. SLAs: This shows the SLA targets on the issue. You will see if any are breached, and if not, how much time has elapsed, and also the time left until the estimated breach date.  This is not shown in the screenshot.


6.5. Commits: This stands for Version Control Commits. If you use a version control software like Subversion or Git in VisionProject, you will see code commits relevant to your issue here. Assuming the issue key was in the description for the commit. This is not shown in the screenshot.


7. Subscribers: You can notify specified users on changes in this issue by adding them as subscribers to the issue. Whenever the issue changes, a notification will be sent to its subscribers, in addition to users given by the workflow. This is a good way to keep an eye on issues of particular interest.


8. Issue History Log: This list shows changes made to the issue over time.

Here you can see exactly how the issue has changed ownership, status, has had new attachments, work logs, or edited fields.

You can sort the History log so you get the newest changes on the top or on the bottom of the log. You can also select if you want to view all changes in the log or Comments only or Changes only.



9. Permissions:  This section shows the permissions on the actual issue, i.e which users, user groups, companies can access this issue. This can also be set to "Everyone" or "Just me".  In the screenshot, this is shown as part of the main issue instead of its own section as it currently is.

User comments
 Loading ...