Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6814875
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T20:44:26+00:00 2026-05-26T20:44:26+00:00

We are reworking on our workflow and looking for options between jira and trac.

  • 0

We are reworking on our workflow and looking for options between jira and trac. We are all comfortable with Trac but have following questions:

  1. What we want is each ticket have 3 people responsible. One developing it, another reviewing it and the third person testing it. We want some advance options that same person cant develop and review / test the ticket.

  2. We want a separate cycle for these three people. Once developed and finished, it goes to the reviewer and tester automatically. They individually can take their set of actions and once it has been approved by both reviewer and tested, it goes to the next stage. Is this workflow possible with Trac. If yes, how should I go about it

Thanks
Sparsh Gupta

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T20:44:26+00:00Added an answer on May 26, 2026 at 8:44 pm

    You can do this with Trac (a team at my company does something similar), but it will take some configuration work.

    First, you need the ability to assign three people to a ticket. To do this, add custom ticket fields (type ‘text’) with names like “Reviewer” and “Tester”. These will be used to store the names of the non-developers assigned to the ticket.

    You’ll also want to add a new state to Trac’s ticket workflow to represent the state where testing and reviewing is being done. For the sake of discussion, I’ll call this state “verification”. Insert this state in the workflow such that a ticket travels from assigned/accepted –> verification –> closed.

    You will also need some way for the tester and reviewer to indicate that they have signed off on the changes. For this, you can add two more custom fields (of type “checkbox”) to the ticket. You can call these “Review Complete” and “Test Complete”. These tickets will default to unchecked and the tester/reviewer will check them once they have successfully completed their test/review work.

    That should get you started as far as the workflow goes. Regarding some of the more advanced parts of your question, you have a couple of options.

    You can add a bit of custom javascript that will prevent a user from being listed in multiple owner fields. The javascript would run whenever the owner, reviewer, or tester field is modified. If the new value in that field matches the value in one of the other two fields, the other field will be cleared out. Instead of writing custom Javascript, one of the following plugins may be able to do this for you:

    • DynamicFieldsPlugin
    • TicketValidatorPlugin
    • TicketSubmitPolicyPlugin
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

We're working on a website. Our client want to check the website daily, but
I'm looking to implement SQL Server Reporting Services as our standard reporting platform in
I'm reworking some PHP code to use PDO for the database access, but I'm
We are currently undergoing some reworking of our website - in the meantime, I
I'm looking into re-working and simplifying our error handling in an application I support.
We're working on revising the url structure for some of our movie content, but
We have an existing Rails 3.1 consumer-facing web app and are reworking the UI
We have a legacy VB6 app, which is critical to our business. We're working
We're trying to do some things on Facebook but to be honest we have
Today we had a lot more activity than normal between our Ruby on Rails

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.