John Funk Community Champion

Controleer het bordfilter om te zien of daarmee iets is veranderd. Controleer ook het subfilter voor het bord om te zien of er iets aan is toegevoegd. Beide zijn te vinden door op het bord naar Bordinstellingen te gaan.

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

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

Hallo @Albert-Jan Eshuis - Welkom bij de Atlassian-community! Wat is de foutmelding? Ontbreken de problemen op het bord?

Hi Meghan - Welcome to the Atlassian Community! When creating an Epic, you need to populate both the Summary and Epic Name fields. Cards show up on Boards based on the filter associated with the board. Is this a Next-gen project? Or a Classic Software project? 

Is there any other information that you are capturing from the user that could help identify the office that should be used?

Hi @tjarcoboerkoel - Welcome to the Atlassian Community! There is very little customization that can be done with Next-gen projects/boards. Particularly, you cannot limit actions by one person versus another as you would like to do in your example. 

Hi Clara, In the Jira Cloud version there is no way to hide those fields. 

Hi Vasco, You can do this with Automation For Jira. Here is some more information on the tool if you are not familiar with it. There are two types of automation: * Global: In the Free version, you get 100 executions per product, per month * Project: In all versions, you get unlimited executions per month Automation Basics:…

You are not being a pain. :-) What is not working for you?

Hi @l.kubon - Welcome to the Atlassian Community! It's a little clunky, but you can create separate screens for View and Edit. Then take the field that you don't want people to edit out of the Edit screen. They can still see it and the value, but not change it. Then create a looping transition on the status (a transition…

I think you need to hope a support ticket directly with Atlassian. Hopefully, they can help you track down where it is coming from. https://support.atlassian.com/contact/#/

Hi Kyle, Is there someway to know what location should be used? Maybe based on the value of another field?

Looks good - just make sure that the Security Level is required on each issue (if you wan that to be forced). 

Hi Samantha, Try something like: Project = ABC and (parentEpic in (ABC-5252) OR "Epic Link" in (ABC-5252))

Excellent new functionality!! Thanks for providing this!!!

Hi David - Welcome to the Atlassian Community! Yes, there are ways to do this. Can you outline exactly what you would like to happen and when? 

Automation for Jira is a separate function from the project automation Here's a little more information: There are two types of automation: * Global: In the Free version, you get 100 executions per product, per month * Project: In all versions, you get unlimited executions per month Automation Basics:…

Hi Devi, I would add the new Issue Types and workflow statuses to the existing Schemes first. Then I would do Bulk Changes to update the values before having the system move them as a part of the migration process.

This is probably the answer. You must be a Jira Administrator to submit the request though. 

Hi Donna, From within Excel it would look something like this: =HYPERLINK(CONCATENATE("https://YOURDOMAIN.atlassian.net/secure/CreateIssueDetails!init.jspa?pid=17611&issuetype=3 Obvously, you would put in your domain. And PID would be the ID of the project and 3 in this case is the ID of the issue type. To find the Issue…

Hi Sergey - Welcome to the Atlassian Community! Try putting a new action for Re-fetch issue before the email. It is probably as Jack suggests that the assignee is not getting fully set before the email goes. 

Hi Nannette - so you added a constraint for an issue type to the new custom field? And you added the field to the screen? And you just can't see it because it has no value in it? I don't use the server version, but do you have to click an Edit button to see fields with no values in them?

It might have introduced the error due to a but with the dates getting applied under teh branch. Give the shortDate a try and if it fails, you should open a support ticket. 

What did you change about the rule from when it was working? 

Hi Dionei, Try: project = ABC AND issueLinkType in ("rework")

try using this and see if it helps: {{sprint.startDate.shortDate}} where you add .shortDate to each smart value. I really think there is a bug. 

Those look like Project automation. Are you also using Automation for Jira? Somewhere, there is an Automation Rule that is doing a transition to Specify. You need to find that rule. 

Hi Yossi, Take them out of the jira-servicedesk-users group. It is that group that makes them an Agent and costs you money for JSD. 

Thanks! One more share - can you show the value of one of the Alors details? I am suspicious about the CEST being in the middle of your date that is being parsed. I believe that is what is causing it to error out.