Tideum JETI (JIRA Enhanced TFS Interface)

 

Tideum JETI pro­vides you with a check-in pol­icy for Team Foun­da­tion Server. If you col­lab­o­rate in a team to develop soft­ware in Visual Stu­dio you need to make sure that every­body is able to fol­low the mod­i­fi­ca­tions being made. The eas­i­est way to keep track of code changes is to asso­ciate your TFS check-in com­ments with already exist­ing Atlass­ian JIRA issues by using Tideum JETI.
JETI checks your TFS com­ments automatically

  • Is there a proper issue ref­er­enced in the comment?
  • Does the issue num­ber exist in JIRA?
  • Does the issue have the right status?
  • Is the project correct?
  • Is the issue assigned to the per­son who checks-in?
  

Save Time and Money

Try­ing to find out what kind of mod­i­fi­ca­tions have been made to the cur­rent soft­ware ver­sion by com­par­ing the code to older ver­sions takes a lot of time.  When (and if…) you finally found the changed parts you still don´t know the rea­son why these changes have been made. Sim­ply use JETI to avoid this time con­sum­ing and inef­fec­tive pro­ce­dure. JETI asso­ciates your JIRA issues with the check-in com­ments, so you just have to refer to the exist­ing issue if you want to know the rea­sons for the changes of this ver­sion. Fur­ther­more, soft­ware engi­neers save time by not hav­ing to come up with long descrip­tions to describe the mod­i­fi­ca­tions. Just type in the cur­rent issue num­ber you´re work­ing on and you´re done. Soft­ware testers will never again waste time test­ing old code ver­sions because they incor­rectly thought that they would already include fixed issues.

Track Changes

Being able to track changes is impor­tant in a col­lab­o­ra­tive envi­ron­ment. With JETI you get an easy-to-use track­ing sys­tem that ensures the qual­ity of your check-in com­ments. It con­nects your exist­ing soft­ware issues with the code mod­i­fi­ca­tions, pro­vid­ing you with a sim­ple method to always keep track of the progress. Instead of mean­ing­less com­ments like “fixed bug” you now get impor­tant, reli­able infor­ma­tion of the rea­sons behind the changes. Another advan­tage of JETI is that you avoid unclear check-ins which con­tain sev­eral dif­fer­ent mod­i­fi­ca­tions. With JETI, one check-in cor­re­sponds to one sin­gle issue. This makes keep­ing track of changes easy and simple.

Improve Pro­duc­tiv­ity

Every­one in your team ben­e­fits from JETI.  Soft­ware devel­op­ers save time and energy by not hav­ing to worry about the trace­abil­ity of their code mod­i­fi­ca­tions. JETI pro­vides them with a sim­ple stan­dard process for cre­at­ing check-in com­ments. Soft­ware testers finally get a reli­able source of infor­ma­tion about the code ver­sion they are test­ing. They can see at a glance which issues have been fixed in the ver­sion they are work­ing on. Project man­ager can not only see the cur­rent pro­cess­ing state of open and closed issues but can actu­ally track the progress of the soft­ware devel­op­ment. By increas­ing the infor­ma­tion flow between all depart­ments JETI helps you to improve team­work and productivity.

Full Con­trol

You can change the set­tings of JEDI to meet your indi­vid­ual needs. Define what kind of infor­ma­tion the check-in com­ment must con­tain and estab­lish the appro­pri­ate input form. You can also decide which kinds of issue sta­tuses allow a ref­er­ence to a par­tic­u­lar issue. For exam­ple, when you choose to just allow the sta­tus “open”, you can only check-in com­ments that refer to an issue with the sta­tus “open”. You can allow and for­bid every com­bi­na­tion of statuses.

Clear and Simple

JETI has a clearly struc­tured user inter­face that allows intu­itive oper­a­tion. There is no knowl­edge in pro­gram­ming or soft­ware devel­op­ment needed to use it. Just log in to your JIRA Server and JETI gets all the infor­ma­tion it needs auto­mat­i­cally. Now tweak the set­tings by sim­ply click­ing the check­boxes and you´re good to go!

Get Tideum JETI now!