Dynamically updated placeholders/values

[Eugen König]

Hi all,

we're migrating from mkdocs and looking for a similar functionality like the "placeholder" plugin in mkdocs. Basically, you can define a a mask with input fields. User puts the data into these fields (or selects a value through dropdown) and it prints a configuration block where the input is dynamically inserted into specified values.

Let's say this is the mask taking two values:

[Customer]: xyz
[IP Address]: 10.1.2.3

Which then prints a configuration block looking like this:

environment: staging
enabled: false
customer: xyz
ip: 10.1.2.3
supervisor: John Doe
whatever: 123456

In the example above, the mask with two input fields and a configuration block were credated. The values from the mask are rendered into the configuration block. As simple as that. Or a bit more complex usage example in the demo link above.

Couldn't find this use case in any plugins (maybe I was looking for the wrong keywords). And not sure, maybe it can be done with a simple macro or something like this? Any recommendations?

Thanks in advance!

[Clark Everson]

Hi @Eugen König 

Where and when is this data being entered? is it for ticket updates? new tickets?

A lot of this can be done via automation but the how depends on the exact when to it. And there maybe multiple automations needed if there are multiple whens

In general though it would be some combination of screens and automation for jira most likely

Best,
Clark

[Eugen König]

Hi Clark. Sorry for the late answer, was out for vacation.

The use case is actually much simpler. The data can be entered directly in the mask on a confluence page. Let's say I have a documentation page, which describes a specific process. The process/documentation includes a description how to create a piece of code for specific use case. To make it easier for the user, he can put in some of the data in the specific mask input fields and the rest is being generated.

So, basically, for the user there is a mask with 1-n values available, which are either selectable by drop-down or can accept a string. In the background, not visible for the user, there are templates of the code available and the values that are selected/entered by the user are rendered/replaced in the code block.

When the user hits the button "Generate" (or anything else), the code block is printed for user for the copy.

This is also a complete use case, no ticket updates nor any other integrations with Jira or other services.

Best,
Eugen