John Funk Community Champion

So there's no problem, correct? You are just curious about the message. 

Hi Robert - Welcome to the Atlassian Community! Yes, that is all pretty standard and straightforward. Do exactly has you have outlined. For Step 2, when the ticket is closed or escalated, you can execute an automation rule automatically to create a ticket in the JSW project and link it back for the original JSM request.…

First, when I say hidden - I just mean that it is not included on the screen. It would be populated by an Automation for Jira rule so you wouldn't need access to it on a screen. Just populate the field with a value when you create the issue using your automation rule. Then use the value of the field in a condition when you…

Use Edit Issue instead of Assign Issue. Choose Assignee and then see if you can copy the value from the Custom Field.

Hi Vineela, Why is that a problem for you? Is the workflow now working? 

Hi Bola, I am not see anything there that should give you a problem. Maybe start small by only summing up two fields and see what happens. Also, you might try using the ID of the custom fields instead of the name to see if that helps. It would look like this:…

Hi Vicki, Validators in workflows work the same for all project types for Company-managed projects. Just edit the workflow add the validator like you would with other project types. 

Hi Maria, Projects in Jira really relate more to a team or a product and not a traditional project. If you work to work like that, you should use Epics for your project work in Jira. Then you can add Start and End dates to it. 

Hi Melana - Welcome to the Atlassian Community! Jira Work Management should indeed be fully functional if you have a paid Jira Software Premium subscription. Are you sure you are in the same instance as the premium account and not a separate Free account? 

Ah, you are in a Team-managed project. That is the reason for the limit. If you need more than that, you should switch to a Company-managed project. 

Hi Morten, No, you will not be able to hide that. 

Hey James, If you are clicking on Delete Permanently and it is not immediately deleting then you will need to contact Atlassian Support to figure out what is going on. https://support.atlassian.com/contact/#/

As a Jira Administrator, you should be able to rename the fields. Go to Settings > Issues > Custom Fields Search for the field and then click on Edit

Hi Jade - Welcome to the Atlassian Community! What do you mean by "amend" fields? 

Hi Florian, Make sure the Summary field is on the Edit screen used by the project. You certainly should be able to edit the Summary field. 

No, you won't be able to see that hierarchy on the board - only in the Advanced Roadmap plan

Was just trying to compare the results of the links with a filter for each type created to see if there was something different about the. Also, can you answer my last question? 

Can you share a screen shot of the rule as you have it now? That syntax that you have is not correct for the field name. Are the custom fields all single user picker fields? They should show up to copy from. 

Hi Laurenz, You must edit the Field Configuration scheme for that project to change the Renderer for that field to Wiki-style.

Correct - built in approvals are only available for JSM projects. 

Hi Kyung, You would need to identify Sub-tasks B and C somehow - probably with a custom field. The field can be hidden from the user, but you would need to use the value for a condition check. Or another solution might be to create a different Sub-task issue type then you could do your condition based on the issue type.…

Hello and Welcome, Adeel! We are glad you are here!!

Hi Michael, There is nothing built into JWM like there is for JSM. So you would have to do a lot of manual adding in of things. For instance, you would need to create a custom field for someone to grant the approval - something as simple at Approved? Yes/No Then you can build some automation rules to do things like…

Hi Kalle, You should be able to do most (if not all) of that now. Have you tried it? Are you running into obstacles?

Hey @Paula Pokusa - Did you give it a try? Did it work? 

Hey @Karl Rothenberg - Did Kurt's response take care of what you needed? 

Hi Emerico, Just to clarify - it looks like you had a space at the end of your label when you got the error message (there's a space after the 2023 and before the end quote mark '

Same here :-)

If you are using Jira Cloud, there should be no extra purchase - I believe it comes included. And I certainly use it and am a big fan of it. :-)

You are welcome