Dick Community Champion

Dear @Thomas N_ The brackets in @Shalini Pradhan 's answer are crucial in finding the correct Jira work items. Please verify her solution by copying it into the filter you're using. Kind regards, Dick

The backlog representation and board use the same (board) filter. The control switch "use epic panel" switches the epics from appearing in the backlog listed (they go to the epic panel instead). Kind regards, Dick

Hi Elena, It would be better to have the epic stagnant (can be in a separate epic board) and let the tasks under that epic be changing according to their progress. The epic may remain in status "in progress", while for each specific date, you let an automation create a task under that epic that defines doing the update for…

Hi @Aggeliki K I believe that this question has been answered by Atlassian's documentation on cascading dropdowns. Kind regards, Dick

Hi @Elena Bertucco Why move an epic backwards, or are you in fact referring to creating an epic at a certain date? Kind regards, Dick

Is that worth a yay for progress ?

Hi @Lisa Mendonsa The way you and I treat the field (with the square brackets) is how one should address an array field. Normal fields like text fields do not require these. Kind regards, Dick

Hi @Kateryna Helrod I often feel people (in general) care too much for semantics. As long as something works for a team, it's more than okay to be different from the rest. Kind regards, Dick

Hi @Lisa Mendonsa Welcome to the Atlassian Community I think you're mixing things up into quite a spaghetti here. :) It all starts from your UDF Free text 1 definition. If it is a text field you cannot put arrays of values in it (that simply doesn't compute). * So start by sharing the custom field definition to check if it…

Hi @Kateryna Helrod Welcome to the Atlassian Community, Your main goal cannot be realized in Jira. Even in the Cloud version, where issue hierarchy can be changed you are not allowed to put an issue type in-between Epic and Story (I tested this). As an alternative, you can have an issue type above epic, ie initiative. That…

@Mohit Edupuganti Can you please share your solution, so that others can benefit that have similar questions please? Kind regards, Dick

That should be ample permission. Does the actor of the automation rule have rights to assign the issue to a person? Access this from within the automation view, then select Rule Details. The actor is usually "Automation for Jira" this entity should have enough permissions.

Yes, the reporter field needs to be accessible, so this is not the answer to your query. Doe the person you want to mention as the reporter in the automation have a project role that allows them to create a ticket? Kind regards, Dick

@Mohit Edupuganti can you make a new project and report back which "version" UI you receive ?

Yes, Marketing, blank template

I just created a new empty marketing project from scratch, team managed from the template and it still doesn't quite look like yours. That's unexpected...

I saw that too. But the regular team managed project isn't quite like yours. this is a team managed business type project (also Cloud): You have Fields where I have Issues types in the menu. Just figuring out what type of project you're running :)

@Mohit Edupuganti No, you access it via Project Settings - Issues - Screens You can click the link of the screen that is used for editing your work item (issue) Kind regards, Dick

Hi @Sharon G_ You find this information in the history of a work item. To access it, I recommend using a plug-in that is to your liking. Use either: * Issue history for Jira described in this great article * or use JXL, which does even more heavy lifting for you. Kind regards, Dick

Hi @Mohit Edupuganti The reporter field should be editable. This means that the screen used for editing the issue should have the reporter field incorporated. You can check this by: Opening the project settings, go to screen scheme and drill down to the screen used to edit work items. Click the screen link and adjust that…

Hi @Star Support So which of the four solutions was the one for you? Just curious :) Dick

Automation is certainly possible. I have no experience with Groovy scripts. Note that you won't get into trouble when the summary is the same for multiple sub-tasks, as their key will be different. Kind regards, Dick

Hi @mummareddy supriya The feedback you get from Jira is quite spot-on here. You cannot have a orphan sub-task work item, it needs a parent. Jira invites you to fill in the parent key, so it can maintain the parent-child relationship you desire (by wanting to change the work item into a sub-task). If you haven't got a…

Hi @Star Support Welcome to the Atlassian Community. The transitions in a workflow (the arrows) can also have a pre-condition that has to be met to allow a transition. Please check that by editing the workflow, clicking on diagram layout, then click on the transition arrow that you're trying to accomplish. You can then…

Hi @Adrian Kornecki Welcome to the Atlassian Community. JQL offers you to use smart values. These are documented by Atlassian. For any Jira work item (formerly known as issue) you can have: {{issue.summary}} , which prompts you the summary string. Kind regards, Dick

Hi @Ziv Ariely Welcome to the Atlassian Community Please refer to the Atlassian Guidelines on this. Kind regards, Dick

Hi @Willyam Mudingayi Malumba , Thank you for elaborating your query. I translate it into you needing a dynamic list of linked issues (parents). There seems to be a similar ticket on this forums. Kind regards, Dick

Hi @Willyam Mudingayi Malumba Welcome to the Atlassian Community. I believe your post isn't getting traction because of an inconsistency in your question. * A Jira work item can only have one parent. The key of that parent is stored in the parent link field. Please rephrase your question with the above in mind, so we can…

Hi @T0pH0ur I'm not familiar with scriptrunner, but you should start by logging the in-between results and proof that a certain piece of script has been executed. This post can help you realize this. Kind regards, Dick