Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Who tracks issues?

Issues SOS keeps the status of issues in the SOS Change Management System are interesting and therefore tracked by two groups of people: up to date for

  • Interested Parties who want to stay on top of information about upcoming releases.
  • Users who reported a bug or feature request in the SourceForge JobScheduler Ticket System or SourceForge YADE Ticket System and who want to track the resolution.
  • Customers who reported a bug or change request in the SOS Ticket System and want to track the resolution.
  • Users from Sourcefourge that have reported a Bug and that wants to follow the resolution of this Bug (the Fix)
  • Customers that have reported a Bug in OTRS and wants to follow the resolution of this Bug (the Fix)

How to track issues?

There are basically three ways of tracking a number of ways how to track issues in the SOS Change Management System:

  • Watching Issues
  • Filter for Customers: Find your own Issues
  • Linked Issues to your OTRS Ticket

Watching Issues

  • (available for registered Users and Customers)
  • Predefined Filters: Find issues related to your individual environment (Customers)
  • Follow Linked Issues to the SOS Ticket System (Customers)

Anchor
watching_issues
watching_issues
Watching Issues (Users and Customers)

Once an issue Once an issue for the reported bug has been created, you have the possibility to "watch" a JIRA Issue in the SOS this. The Change Management System . JIRA will then send you a notification by email whenever anyone updates the watched contentnotifications by e-mail whenever the watched issue is updated. You will receive email notifications for:

  • Edits 
  • Deletions
  • Attachments
  • Comments

Example:

...

Predefined Filters : Find

...

issues related to your individual environment (Customers)

 

If you are a customerCustomer, you may like might want to create a Filter where you can  from from time to time keep time you can keep track of the status of the bugs you reported. For that goal, you would do the following:

  1. Go to "Issues" on the top of the page
  2. Click on "Manager Manage Filtes"
  3. Go to "Search" and on the field "Search" look for "customer"
  4. The filter "Filter for Customer" should apperappear:
  5. You just click on that filter and go to "Save as" and give it the name you want to. Now you are the owner of this filter and it is only customizable by you.
  6. Change the last field in the search, so that where it says "ACCxxxACCxxxx" you indicate your real Customer Account Number and Search for Issues(where to find my Customer Number (question)
  7. Carry out the search and finally After all you have to "Save"

Example:
Image Added

 

Hint: Automatically after you saved this filter it will appear for you in the System Dashboard in the section "Favourite Filters"!

Anchor
account_number
account_number
Find your Customer Account Number

Customers will find their Customer Account Number (in the form "ACCxxxx") in the SOS Tickeet System web interface where they originally created the tickets. On the upper right part (under the logo):

Image Added


Follow Linked Issues to

...

the SOS Ticket System (Customers)

Another possibility for Customers to tracking track issues from bugs they reported in OTRSreported from the SOS Ticket System, is to look for the JIRA Issue issue containing the Ticket Number in OTRS. For that goal you need to do the following:

  1. Navigate Go to "Issues" on the top of the page
  2. Click on "Search for issues"
  3. Go Navigate to "Project" and check "TIC - Trouble Ticket Management"
  4. In the Search go panel navigate to "Contains text" and indicate the Trouble Ticket Number

This issue you will be directed to is just an interface between the issue you want to track in JIRA (the Fixfix or feature)) and the bug incident or change request that you reported in OTRSthe SOS Ticket System. The Fix is the linked issue you will find in the original issue you have searched for, where you access from.original ticket can be accessed like this: 

Example: