John Funk Community Champion

You are not going to be able to get around that the Summary field is required. What I don't understand is why you don't want to populate it. It is the title of the card and used throughout the system. What is the problem with letting the user populate it?

Sorry, that I couldn't help get this solved. I would go ahead and open a support ticket with Atlassian here: https://support.atlassian.com/contact/#/ If you don't mind, please come back here and update when you have a solution. Thanks!

What do you mean by "taking out the Summary field from a specific issue type"?

Did you try this? I've found it, completely by accident. * Go to your board * Hit the 'Board' button on the top right * Hit 'configure' * On the left hand side, under 'configuration' press 'Issue Detail View' * Under 'General Fields' choose your custom field, and hit Add.

Hi Roman - did you try typing the entire name? Or using the username instead like roman.zigo?

Hey Nadia - can you include a screenshot of what you are seeing and needing changed?

I would try to move to a classic project and see if that works. Again, I would make sure that the fields are available to both projects. 

You might try reading through this post: https://community.atlassian.com/t5/Jira-questions/How-do-I-display-custom-fields-in-the-detailed-issue-view/qaq-p/401589 It might be that you need to add the field to the View screen. But not sure. I don't use server so not sure if that can even be changed. 

Awesome - thank you and good luck!

Yes, that is true - you would need to change the sharing of all filters and dashboards.

Hola Andres!! ¡Bienvenido a la comunidad de Atlassian! Nos alegramos de que usted está aquí.

Hi @vcatl2020 - I am pretty positive you are correct that the Summary field is not a field that you can do bold or other Wiki type edits. You can have the system set the Summary field upon create to whatever value you like. However, it will not show a default with a value in it when you hit the create button. But, what…

Hi Timothy - can you show some screenshots? I have not noticed that. 

Hi Meghna - Welcome to the Atlassian Community! Not sure why are you losing things during the move unless there are fields that are in the Service Desk Project that are not available in the Next-gen Project. Or if during the move there are fields that are not getting marked somehow to copy the values. Regardless, have you…

Hi Riana - Welcome to the Atlassian Community! Yes, I am afraid the process as you describe above. You would basically need to create a new group in Jira (something like Internal Users) and put all of your users that you want to see all projects in that new group. Probably meaning all of your current team…

Hi Sebastian - I just tried a test of this (deleted the clone) and it did not delete the original issue (Epic). Now, having said that, it is rarely a good idea to delete an issue. It is better to mark it as Discarded or Canceled or something like that. 

Hi Madhu, Maybe try: {{issue.comments.last.body}}

Hi Robert - This is currently not available in Next-gen projects. You can vote for the feature request and follow along here: https://jira.atlassian.com/browse/JSWCLOUD-17450

Hey Phil - Welcome to the Atlassian Community! It should have still worked, even with 1700 - but there's a good chance that's the problem. So first question - then it needs to move to the new workflow, are their statuses that exist in the current sub-task workflow that do not exist in the new workflow. 

Hi Alfred, Maybe try something like this: issuetype in (subTaskIssueTypes()) AND "Parent Link" in (ABC-123) where ABC-123 is the key of the parent. 

Maybe @John McKiernan can help explain why it doesn't work in the second sub-task. I have seen that happen with others before. In the meantime as a quick fix, you might try adding a Branch Rule/ Related Issues component at the end and use Most recently created issue. Then add an Edit issue component and update the Assignee…

Was interested in the answer myself. Ha! Thanks for jumping in here to provide your usual great support and service!!

Hey Nathan, Can you provide a screenshot of your rule?

Sorry - I use Cloud, so not sure of other alternatives for Server/Data Center. I know that ProForma Forms has an option with their forms to connect to an external data source. 

Great - Glad I could help!

Hey John, Did you try to use the JQL with a non-Next-gen project to see if you get results?

Hi Richard, Click on your avatar in the top right. Then select Turn off the New Navigation.

@John McKiernan 

Glad I could help!

Hi Alex - Welcome to the Atlassian Community! I will try to answer each of your questions. 1. Roadmaps are linked to Epics. But roadmaps are currently only available for Next-gen type projects. The roadmaps are just a visual depiction of some information about the Epics. Boards allow you to visually see the issues (cards)…