Issuetrak Product Feedback

Issuetrak’s success relies on tight collaboration with our customers. Tell us, how could we make your life better with Issuetrak?

I suggest you...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Waiting for Customer Response  ·  1 comment  ·  Business Rules  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add more 'Issue Events' to Business Rules - Substatus Rules.

    Only 'Note added by Submitter or anyone in Submitter's Organization'. This Issue Event option should be expanded to include 'Note Added by Next Action or Note Added by Assigned to'.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Approved (Timeframe TBD)  ·  0 comments  ·  Business Rules  ·  Flag idea as inappropriate…  ·  Admin →
  3. More Conditions for Substatus Rules

    Allow additional conditions for Substatus Rules, such as Organization to add more flexibility.

    For example, having the following would help create a trigger when their internal Agents from a particular Organization, Department or Group triggers an Event:

    Issue Event: Add Note
    When Substatus Equals: Customer Response Received
    (NEW) Group: Internal Agents
    Set Substatus To: Pending Customer Action

    This would allow their designated internal Agents to automatically trigger the Substatus to "Pending Customer Action" when they add a note, while preventing the Submitter from triggering the same Substatus Rule.

    Reference Support Issue: 104286

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received (waiting for review)  ·  0 comments  ·  Business Rules  ·  Flag idea as inappropriate…  ·  Admin →
  4. auto assign to agent with fewest number of open issues

    Worked with Jiten with Charles Tyrwhitt Shirts Ltd.

    They would like the ability to configure Auto assignment rules to assign new issues to an agent from a list agents that have the fewest number of open issues. Currently, a user is manually assigning to accomplish this task but they would like to see it automated in the future.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received (waiting for review)  ·  0 comments  ·  Business Rules  ·  Flag idea as inappropriate…  ·  Admin →
  5. Business Rules: ability to notify a specific role when any field is changed

    It would be useful if escalation rules allowed adding a rule to send an outgoing note to any specified role on an issue(e.g submitter, or a specific group/user ) when any specified field is changed and provide the new values in the notification.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received (waiting for review)  ·  0 comments  ·  Business Rules  ·  Flag idea as inappropriate…  ·  Admin →
  6. Auto assignments should be in its own section/category

    Auto assignments should be in its own section/category instead of inside of Business Rules.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received (waiting for review)  ·  0 comments  ·  Business Rules  ·  Flag idea as inappropriate…  ·  Admin →
  7. Ad-hoc Escalations

    Ad-hoc Escalations

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received (waiting for review)  ·  0 comments  ·  Business Rules  ·  Flag idea as inappropriate…  ·  Admin →
  8. 4 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received (waiting for review)  ·  0 comments  ·  Business Rules  ·  Flag idea as inappropriate…  ·  Admin →
  9. Allow substatus rules to be fired based on ticket type

    It would be great if substatus rules could be tied to a ticket type if required. For example with a ticket type of: "Change Management" I may have a rule that sets the status to "waiting for approval" based on a ticket event of "assign" but on a "Problem" ticket type I would want a rule that sets the substatus to "investigating" based on the ticket event of "assign".

    3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received (waiting for review)  ·  0 comments  ·  Business Rules  ·  Flag idea as inappropriate…  ·  Admin →
  10. Priority Hierarchy by IssueType

    Have a different list of Priority levels by Issue Type

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received (waiting for review)  ·  0 comments  ·  Business Rules  ·  Flag idea as inappropriate…  ·  Admin →
  11. Option for SLA terms to follow Hours of operation.

    In current functionality you can set the terms of a Service Level Agreement for either 24 hour coverage, or set hours of coverage. I would like to see a 3rd option added so that the coverage can follow the hours of operation.

    This would save our users a lot of work in setting things up.

    3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received (waiting for review)  ·  1 comment  ·  Business Rules  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base