John Funk Community Champion

You won't be able to do that with the avatar/picture, but you could create a separate quick filter for each person. 

Ah, so that's the Request Type itself. Go to Project Settings > Request Types Then click on the Request type name (Submit a request or incident in your case) Then click on it again to change the name Then click on the Request Form tab. There you can change the Request Form Description. And add help and instructions if you…

Hi @Özge K_ - Welcome to the Atlassian Community! You can do that with an Automation for Jira rule that would fire on create of the issue. Then add a condition to check if the End Date is not empty. And if not, then transition the card to Done. 

Hi Monica - Welcome to the Atlassian Community! What do you mean by transition states? Can you share a screenshot of what you want to remove? 

Can you share a screenshot of the part you want to change? I think I might be confusing things. 

Good podcast! But I found the arguments against internal hackathons to be fairly weak. We do internal hackathons periodically, but it is done off site from our offices typically, and involve the entire product engineering team (more than 200 developers) as well as product managers, project manager, marketers, etc. It is…

Hi Chris, Can you share what you have tried? There was nothing attached to the question. 

Hi @akavanagh - Welcome to the Atlassian Community! You should be able to go to Project Settings > Portal settings and make the modifications you need. 

Sorry - you are going to need to open a support ticket with Atlassian then. https://support.atlassian.com/contact/#/ Please post back here with the resolution - I would love to know what they say. 

Are you using Outlook in the Cloud? Or local client? And if local client - is it Windows or Mac? 

Hi Domi Those colors are based on the Status Category of the status and serve a purpose across the application. You are not going to be able to change the colors of those. However, you can change the color of the card on the board based on the status if you like. Go to Board Settings > Card Colors and put in a query based…

Try removing the fields from the Agent view at the top in your video, but leave them in the Client tab at the bottom of the screen. 

Here ya go: https://jira.atlassian.com/browse/JSWCLOUD-21916

Hi @iamkelsishayla - What kind of error are you getting? What type of project is it? 

Then I am not aware of another open feature request. :-(

@felix.weber - So you are saying that works for you? 

Did you add fields from the Client tab to the Request portal form? It looks like that is yes. But the is also an Agent view form - can you post a screenshot of that? 

Hi Mike, Typically, gadgets are based on a filter and it is the filter that determines which issues will show up. Boards are also based on filters, which are more than likely different, which means different issues show up on them. So, you will need to create/use a filter for the gadget that includes all of the cards used…

Maybe try this: { "fields": { "customfield_14901": { "id": {{initiator.accountId.asJsonString}} } }, } If that doesn't work, try changing out your customfield value with assignee and see if that works. If so, then there is an issue with your custom field. 

Hi Ann - Welcome to the Atlassian Community! Create a new custom field of the User Picker (multiple users) type. Then you can place multiple users in that field. However, you cannot have the issue actually assigned to more than one person in the Assignee field. That's not going to change anytime soon, if ever, so you will…

And we certainly don't need more Funks!

Sounds good - best of luck!

Hi Soham, What happens if you remove the asJasonObject part?

Hi Mark - Welcome to the Atlassian Community! Sorry but no, that is not possible. 

Hi Jamie, I usually decide on projects based on the team. If there is one team working all of the stuff, then one project. If multiple teams or squads with totally different products, then different projects. 

Hi Greg - Welcome to the Atlassian Community! I would probably add a new status to your workflow so that all issues that get created go into this new status first. Then you can move them to Backlog status. 

Hi @Gerardo Romero - are you still having this problem? @Tamra Avery - any update? 

@Sebastian Penhouet - I am not sure as I don't really use Team-managed projects. And not sure if this covers it, but here is an open request: https://jira.atlassian.com/browse/JSWCLOUD-17336

Hi Ali, Did you get this solved, I see that the question was posted a while ago. 

Ah, that would explain it. Here's some general guidance for that. You will need to create a filter for the Team-managed project, something like Project = ABC ORDER by Rank ASC where ABC is the project key for your Next-gen project. Be sure to save the filter and share it. Or you can use an existing filter if one exists…