John Funk Community Champion

That usually means you have not published the workflow after you added the status. Please also confirm what type of project you are working with. 

Hi Sona - Welcome to the Atlassian Community! What type of project is it? If Next-gen, just add the column and it will add the status automatically. If Classic Software, add the status to the workflow, then edit the board to map the status to the column. Be sure to publish the workflow after you add the status. If Business…

Actually, you might try this first: https://community.atlassian.com/t5/Jira-Core-questions/I-can-t-delete-permanently-a-project-from-the-trash-Why/qaq-p/1366826 Log out, clear cache and go back in basically. 

Hi Idan, I would go ahead and open a support ticket with Atlassian: https://support.atlassian.com/contact/#/

Hi Seema, You will need to remove the Resolution field from the Create screen. But you will probably need to be a Jira Administrator to be able to do that.

Hi Seema, Make sure you publish the workflow. I think that is what you are missing. So edit the workflow and once there, then click on the Publish button.

Hi Seema - I see the pencil on the right hand side. Is it not available? Also, have your Jira Administrator verify that the workflow is not shared with any other projects. Just because it has the word Simplified in the workflow name doesn’t mean that it might be shared somewhere else.

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

How many users do you have for each product? Can you show a screen shot? 

Hey Brennan -Welcome to the Atlassian Community! The Business type projects do not have a board settings function, and therefore, you cannot edit the board in anyway except by adding statuses to the workflow. You would need to migrate to a Classic Software project. 

Hi Randy, Whether you can change the Issue Type directly or whether you have to use the Move function depends on what Issue Types are attached the current workflow being used by the issue. If this is the only issue type attached to the workflow, then you will not be able to change the issue type with the simple dropdown.…

Just the screen when you click on the Create button.

Hi Francisco - Welcome to the Atlassian Community! First, you should always create new questions in Community so everyone will see them. When you post to a very old post, only a couple of people will see your question. Something to look at is to make sure you actually change out the board filter that is associated with the…

I can't answer that - I just know what you need to do right now to fix it. :-)

Hi Linda - Welcome to the Atlassian Community! One thing to try would be to click the Configure Fields button while in the Create screen. Then click on Where's my field? Type in your field and see what response you get back. 

Since you are populating 90% plus with the Epic data, why not add automation to Clone the Epic to another Issue Type, and then Edit the Clone? Just as a side note, there is no Scrum type of project, just Scrum boards. Project types are either Classic Software or Next-gen in this case. With Classic Software, I would try the…

Hi @Admin Vicinato - Welcome to the Atlassian Community! There are also limits on the other products, such as JSM, Confluence, etc. JSM Free only allows for 3 persons. So check the number of users you have in those other products as well. 

Hi @Stephane Zoko - You will definitely need an add-on. I would personally suggest Proforma Forms. https://marketplace.atlassian.com/apps/1215833/proforma-forms-checklist-for-jira?hosting=cloud&tab=overview

That's my point - you can't remove issue types from the Default Issue Type Scheme. By nature it includes ALL issue types. The only way to remove an Issue Type from the Default Issue Type Scheme is to delete the individual issue type. 

Hi Amruta, The Default Issue Type Scheme will by default all all new issue types that get created. If you have a project that you don't want all of the issue types to appear in, then you need to copy the Default Issue Type Scheme, give the new one a new name and remove the issue types that do not apply. Then apply this new…

Ah, that makes sense then. What type of project is this? I assume that you are firing this on the child getting created and you want to copy down the value from the Epic. Correct?

Have you tried to update the field just using the standard field update and not JSON?

Haha - happens to the best of us. ;-) Glad you got it solved!

Hi Graham - Welcome to the Atlassian Community! Take a look at this document and see the Labels section. https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-fields/

Hi Angie, See if this previous post helps you: https://community.atlassian.com/t5/New-to-Jira-Service-Management/How-do-you-restrict-a-customers-access-to-only-their-requests-in/qaq-p/1313568

Oh - it probably went to the Backlog, which is off of the board in most cases. Click on the Backlog menu option on the left hand side on your board and you should be able to see it. If you still don't see it there, then you need to check the board filter associated with the board to see if it is excluding the issue for…

Hi @Elizaveta Marchenko - Welcome to the Atlassian Community! I would report this as a bug to Atlassian: https://support.atlassian.com/contact/#/

Hi Prabhu, You should use a Scheduled trigger rule in Automation for Jira. Then add your JQL for the issues. Something like: Project = ABC and status change to Open after startOfDay(-2) and priority = High Just replace the values with your actual values. 

Hi @[deleted] - Welcome to the Atlassian Community! So it works if you click the Create button, but it does not work if you try to create the issue from within the Backlog - correct? That sounds like a bug to me. I would put in a support ticket with Atlassian: https://support.atlassian.com/contact/#/ Please post the…

Hi Krister - If you want to retain the current value and just append the new value in, then place {{issue.Process}} before the new value. That way it will keep the current value and add the new value. Of course, you can switch the order around if you want the new value first.