Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.
Restrict access to this artifact for the following user groups:
List of items referenced by or referencing this item.
Artifact Tracker v5
Yes, we do agree on not segregating front/back unless it is necessary. Fortunately, for this change we will not be altering the way old code behaves, it consists mainly of adding rather than modifying. We have tried to come up with propositions (attached file) on how are we going to divide the feature with a focus on having a functional feature from the first change that gets enriched later. How can we improve the proposed changes?
We are not really fan of front/back split because they are often really tight and nourish themselves.
What we are used to do is:
You could for instance start by having a fixed grace period "1 week" for instance, not configurable. With that, you could even implement most of the logic without having to deal with the multiple values. But I don't know if it's small enough.
And, in any case, as ususal, if there are refactoring needed to introduce the new features they must come first. That is to say, if you plan to modify a code that was not already ready to receive your modification, you need to make it ready to accept modification first without introducing new features.
Hello, I would like to know what you think about the criteria to be used in dividing this story into multiple changes. The story as it is been developed now, consists of:
Is this dichotomy the best suited ?
Of course, I am currently working on #13810
I would set that in a new table dedicated to this feature.
But could be please finish story #13810 first ?
I have a question:
If I am to set the reactivation period for two users:
This information becomes a user-specific field. How will we store it in the DB?
Just to let you know, you should not add new variables to local.inc, variables should be managed with `tuleap config-set` with values stored in DB nowaday.