How to extract first letter of each word in summary to use in other field?

[Steven Johnson]

Hello, I am trying to figure out if I am able to extract the first letter from each word, within a story summary name, to use as an acronym in the subtask field?

An example of what I am trying to do:

Story Summary: Example Story Summary Extraction

So the letters "ESSE" would be extracted, and I would use them at the beginning of newly created subtasks (using automation).

Subtask 1: [ESSE] Subtask 1

Subtask 2: [ESSE} Subtask 2

Is this possible to do using JSON smart values? I ask that because I do not know how to use python and do not have access to any of the third party apps.

Thanks!

[Alex Koxaras _Relational_ · Accepted solution]

Hi @Steven Johnson 

You can get that if you write this:

{{#issue.summary.split(" ")}}{{left(1)}}{{/}}

And if you want to get exactly what you wrote on your question, then type this:

[{{#issue.summary.split(" ")}}{{left(1)}}{{/}}]

The above will get you the acronym of the parent task in square brackets. If e.g. you have a summary called "This Is My Summary", then the above will result i:

[TIMS] 

Let me know if you need anything more. :)

Alex

[Tessa Tuteleers]

@Alex Koxaras _Relational_ , 

cool! I couldn't figure out the syntax either, thanks for the help! :D 

[Steven Johnson]

@Alex Koxaras _Relational_ 
WOW!! I started going down a path that was WAY too complex and was hoping it could be something like this.

This works perfectly, thank you!!

[Steven Johnson]

@Alex Koxaras _Relational_ 

I do have one other question in relation to this. It's not as important, but I was curious if lower case words can be excluded from the acronym? For example, the summary "Enhancement to Question for Acronyms" could be EQA instead of EtQfA?

That's probably getting into the more complex area of using arrays or functions or things that I have no knowledge of, but thought I'd ask just in case.

Thanks again!

[Lucas Modzelewski _Lumo_]

Great answer @Alex Koxaras _Relational_  !

@Steven Johnson I was wondering why do you need it, and maybe it's for the visibility of subtasks in some list when relation to parent is not obvious. 

With acronyms sooner or later you will end up with some duplicates eg. ESSE can be different from ESSE. If you need unique identifiers maybe consider using parent issue key - even stripped from the project - leaving only number -> then it will be unique. eg.  parent with key PM-1, in subtasks could be [PM-1] or [1].

Or even combine solutions for readability Id + acronym eg 1-ESSE, 23-ESSE or ESSE(1), ESSE(23)