John Funk Community Champion

Creating a project based on a previous project will not create a board (nor copy the existing one). So if you like the board of the existing one, you can copy it, then change the filter to use the project of the newly created project. Or you can create a board from scratch based on an existing project and use the new…

Hi Andrew - Welcome to the Atlassian Community! I will see if someone from Atlassian can take a look for your. It's typically because their email address gets blacklisted from some reason by Atlassian. 

Hi Martin - Welcome to the Atlassian Community! You can't really link projects, but you can link issues between the projects just like you can issues between two JSW projects or two JWM projects. The process is the same. Can you give more details about what exactly you are trying to do? 

Hi Abdullah - Welcome to the Atlassian Community! Go ahead and add your new issue type to the issue type scheme for the project. Then add a new Field Configuration for the new Issue Type in the Field Configuration Scheme. Here is more guidance on how to do that.…

Hi Jean, Two things - are all of the cards (both parents and sub-tasks) in the last column on the board? That's the only thing the sprint considers done, regardless of the status. Also, you need to add a post function to set the Resolution on the transition to Done. That's what causes the strikethrough. 

It should be there then. Can you share a screenshot? Also, is the context for the field included for the project used by the filter? 

Hi Dmitry - Welcome to the Atlassian Community! What type of project is the existing one that you are copying from? Does the existing project indeed have a board? If so, you can just copy that board. 

Hi Jemima - Welcome to the Atlassian Community! You shouldn't need the word "value" anywhere in your smart values code. So try this: * {{#=}}{{issue.Sample probability (1-5)}} * {{issue.Sample impact (1-5)}}{{/}} Or * {{#=}}{{issue.customfield_xxxx}} * {{issue.customfield_xxxx}}{{/}}

Hi Harsha - Welcome to the Atlassian Community! Sorry, but that is not going to be possible. Team-managed projects are very limited, and you will not be able to create another sub-task type. 

Hi Esmeralda, Is this a Jira Service Management project? 

See if you can change your rule so that it is something like this: My labels field would be your custom field. And my individual conditions would be for each one of your issue types. 

Let's see what we can do. :-) What type of field is the custom field? 

Just got through with a lovely lunch of Indian food and I am at peace. :-)

Hi Jordano - Welcome to the Atlassian Community! Can you share the filter that you have so far for project A? Basically, you will want to update the filter to include the tickets from project B. So, if your current filter for project A is something like: Project = ABC then you will update it to be something like: Project =…

Well, it should definitely show on the screen, even if it is not on the edit screen. You should click on the Configure button at the bottom right and see if the field shows up in another section, like hidden when empty or in the hidden fields section. 

Hi @anjitha.s What type of fields are the custom fields that are not showing up? They must be Select List or Radio Button, or User Picker for them to show up. 

Well, it's kind of like the field is taking on the attribute of the view screen while the user is in the edit screen. I know that sounds weird, but that seems to be the way it works. There used to be 3 separate screen accesses under the OLD issue view, but not really in this NEW issue view. I guess the point is that if you…

Hi Sasa, A quick fix would be to add a validator to the transition to prevent the user from moving the card if the Test 1 field is empty. 

You would need to update your board filter to not show issues that are in the statuses mapped to those columns.

Welcome, Connor! Yes, I think you will find the forms VERY easy to build and super helpful!

Hi Abhay - Welcome to the Atlassian Community! Try an automation rule like this (where you use your project instead of JIRA in my example). You might also want to try that with a single issue first to see if it works as you intend it. 

Ah, that would be it. I verified in my free instance that I cannot share with Public. 

Hi Shine, What type of project are you using? Company-managed? Team-managed? Jira Work Management? You should be able to add Quick Filters to the board to do that. Go to Board Settings > Quick Filters. 

Hi Andy, Maybe @Jane Yeoh can help answer. 

Hi @Santiago Garzon - Did Trudy's response answer your question? 

I would go ahead and open a support ticket with Atlassian: https://support.atlassian.com/contact/#/ Please post back here with the resolution. Good Luck!

Hi Mikhail - Welcome to the Atlassian Community! Many times this results from Atlassian blacklisting the email addresses for some reason. I suggest you open a support ticket with Atlassian to see if that is the case. https://support.atlassian.com/contact/#/

Hi @Pedro Henrique Barreto Carvalho - Sorry for the delay. What type of field is customfield_10620? Why don't you just do an Edit Issues action and select that field for the update? Do you have a screenshot of the Issue Types for the project?

Is this a Jira Service Management project? Or something else? 

Hi Beto - sorry, but no, it is not currently possible to change the timeframe. Please click the Give Feedback button on the bottom left of the project to let them know you would like to hide cards on a board on demand.