Putting {ID}_SEG_{Title} in the File Name is not substituting the title tag. It is only replacing the ID tag.

[fpdutra]

when setting up, if you put a {Title} in the file name field, the tag will not be replaced. Ex.:

{ID}SEG{TITLE}

[stutton]

Full tag replacement was not implemented on the file name field. I would also be concerned that the title of a work item may not make a good file name as they tend to be long and contain spaces.

[fpdutra]

It makes sense not to put the Title there, but either way, it is a nice feature to have.

[mrbcmorris]

Might be helpful to have inline documentation that the {ID} field is the only thing replaceable. It's not very clear from the UI what the options are for naming files

[fpdutra]

Maybe we can put a functionality to dynamically name the file. We can put as an extra field and then apply that to the filename.

[mrbcmorris]

@fpdutra If you can provide some examples it may help me to understand what you’re looking for. Work item titles feel like they would get rather lengthy for a file name. Windows has some legacy restrictions on max file path length

[fpdutra]

for example. If I want my output document that is going to be attached to the PBI to have the following name
{ID}-SEG-{SmallDescription} and i want a case by case Small Description.

That is not possible with the current functionalities of the program.

If i have a case called Change Label text, i want the SmallDescription to be "ChangeLabelText", for example.

But i also want to be able to use the same template and type a different description for a different case.