Have you ever dream you can customize as you (really) want your trackers? Say goodbye to waiting for administrator approval. With Tuleap tracking system, you can configure your project trackers, yourself, at project level. Fine-grained permissions, workflow and triggers, field dependencies, specific user groups, you get the full control. Sounds too good to be true? Come to this talk, you’ll get your smile back. We play here familiar scenarios, unadapted, frustrating ones and we’ll show you how they can be fixed with Tuleap trackers configuration settings.

1. Tuleap Trackers: when one size
does not fit all
Marie-Ange GARNIER, Enalean
Matteo MAZZERI , Enalean
Mathieu AUVRAY, Enalean

2. Tuleap Trackers: when one size does not fit all
Trackers in Tuleap

3. Tuleap Trackers: when one size does not fit all
DISCLAIMER
Any resemblance to existing persons and companies
is purely coincidental

4. Tuleap Trackers: when one size does not fit all
It is well known that …
… all projects work the same way
Because we use the same
tracker for 10 projects
Why the field component is
displaying values that don’t
match our project ?
Dev PM

5. Tuleap Trackers: when one size does not fit all
Let’s Tuleap that !
‣ Make corporate tracker templates and customise them in your project
workspaces
‣ Think « shared fields » to re-use custom fields you already made
DEMO

6. Tuleap Trackers: when one size does not fit all
It is well known that …
… end users always report their issues
I never find your bug
tracker, I loose to much
time
You never said you had an
issue, why are you not
using the Bug Tracker ?
UserDev

7. Tuleap Trackers: when one size does not fit all
Let’s Tuleap that !
‣ Use service bar on the left of the project space to create short-links
‣ Improve productivity with well-positioned widgets
DEMO

8. Tuleap Trackers: when one size does not fit all
It is well known that …
… trackers are easy to use
What the F*** !
How can we fill this s*** ?
I give up !
All fields have a purpose.
We need to keep them as
is. I can’t remove them
PMUser

9. Tuleap Trackers: when one size does not fit all
Let’s Tuleap that !
‣ Use permissions to hide fields in your tracker
‣ Use workflow transition to force value to be set at certain stages
‣ Make your artifact more understandable and readable using
columns, separator and text
DEMO

10. Tuleap Trackers: when one size does not fit all
It is well known that …
… all bugs are critical
Critical ? When did I say
they are critical ?
You need to prioritize your
bugs, they can’t be 100%
critical
UserDev

11. Tuleap Trackers: when one size does not fit all
Let’s Tuleap that !
‣ Use default values in your tracker fields to ease submission
‣ Make key fields as « required » to underline what is important to you
‣ Use fields description to help users fill an artifact
DEMO

12. Tuleap Trackers: when one size does not fit all
It is well known that …
… bugs are always up-to-date
Pffff, I didn’t have the time
to fill this information, you
can do it by yourself
You forgot to set this data
in the bug you fixed to
send stats to customers
DevPM

13. Tuleap Trackers: when one size does not fit all
Let’s Tuleap that !
‣ Workflow transitions can be computed to set values automatically
‣ Think Cardwall or Kanban to make more visual and easy to use
DEMO

14. Tuleap Trackers: when one size does not fit all
It is well known that …
… users are always updated
Your bug ? But we fixed it
last month, you were not
aware to that ?
Can you tell me when my
issue will be fixed, my
project is postponed
User PM

15. Tuleap Trackers: when one size does not fit all
Let’s Tuleap that !
‣ Create one or several Project Dashboards, by sub-team, by topic.
This helps to get easily the information they need.
‣ Run advanced queries and custom-made project reports using
Tuleap Tracker Query Language (TQL)
DEMO

16. Tuleap Trackers: when one size does not fit all
And you, what do you really want
to achieve?