Aiden Marriott_za2e2r Specialist

Hi Bjarke - I don't think there is a way to change how sub-tasks are displayed from the parent task, unfortunately. You could probably use components or an automation rule to assign automatically, but no easy way to change sub-task data in line from a parent task.

@Mike Rathwell @[deleted] - I agree if you have 5-6 developers working on a project they could spin up an Atlassian cloud instance and pretty much run it themselves no problem. Its when you get into large set-ups with lots of different use cases and project configurations that problems occur. There needs to be a careful…

Does this help? https://confluence.atlassian.com/jiraportfolioserver/coloring-issues-on-your-timeline-968677318.html

"Dumpster fire with extra hobos" - Love it, I am going to steal that line! I feel your pain, I have seen the same situation myself.

Go to the "Issues" tab rather than this backlog view. When there you can use the basic or advanced search to try and find what you need (specify a specific project to control results)

In your project admin settings look for "permissions" and edit the scheme. There should be a "delete issues" option which will probably have no-one set. If you edit that and set to the Jira admins group, or yourself personally - you should then be able to delete issues.

Hi GameDev - do you have the delete option appear for normal tasks? If not - you may not have the "Delete Issues" privilege in the project - even System Admins can be excluded for doing this (but they can assign themselves the permission in the relevant scheme)

https://community.atlassian.com/t5/Jira-Software-questions/How-does-one-delete-sub-tasks-or-issues-on-next-gen-projects/qaq-p/1156837

Do the issues have a "fix version" value and if so is that version released?

Is there a Kanban board sub-filter that may exclude the issues? (e.g. you have a release version present). Does the JQL you refer to show any results in the issue search

Are the issues in the backlog view or in a status that isn't present in the board config?

f this is a standard project - make sure "Epic Link" is on the screen If its a "Next-gen" project you change it by selecting the "edit epic" in top left of the issue:

.

That is application access, not Assignable User... just trying to understand by what mechanism you are controlling who can be assigned a ticket. If any user can be assigned, what is blocking them assigning it to themselves? A workflow condition? 

Does look like it is returned by the API by default. There is a suggestion here https://community.atlassian.com/t5/Jira-questions/how-to-get-last-issue-update-for-all-projects/qaq-p/1253839 to bring back the last updated issue from a project, but you would need to go through each project in turn. If you find a neater…

What is your setting for "Assignable users" in the permission scheme of that project?

I would start by thinking about how you would achieve this in Java (which jar files, drivers etc would be needed), what does the code look like. Scriptrunner uses groovy which works in the Java VM... its not quite the same as Java but you often can directly re-use your java code. If you arent comfortable with coding you…

Boards are based on underlying JQL filters so you can probably identify all the issues that are included easily enough (e.g. filter in (... ) ) and maybe compare in excel or try and extend it to some kind of not in JQL 

Sounds like you havent published your workflow. Also issues will go to the backlog by default unless you have given it a "Sprint" value on creation

What type of custom field is it?

You will need to use the incoming mail handler set up with a default reporter: https://confluence.atlassian.com/adminjiraserver/creating-issues-and-comments-from-email-938847641.html#:~:text=Once%20you%20have%20configured%20Jira,open%20the%20Incoming%20Mail%20page.

I don't think its possible in standard Jira software. ScriptRunner "Issue Picker" custom fields let you use JQL to limit options available... there are probably other options out there that will do something similar if you don't need all the features scriptrunner provides

Usually anyone who is a participant or a makes a comment/is mentioned would be an issue watcher (dependant on settings)... so maybe watcher = currentUser() would work?