John Funk Community Champion

Hi Jose - Yes, I do it by creating a group and adding only certain users who are project administrators to that group. Then that group is added in the System Settings for who can create rules. 

Hi Bhagya, When you go to Board Settings > General, do you see this at the bottom? 

Hi Navin - Welcome to the Atlassian Community! You cannot add questions to the built-in survey in Jira. It is intended to be very simple and basic. There are add-ons that you can find in the Atlassian Marketplace that will help you with the items you want. Apart from an add-on you will not be able to do those things. 

Hi Derek - Welcome to the Atlassian Community! Are you specifying the Issue Type in the CSV file? (i.e. is there a column for Issue Type in the CSV file?) Or just letting it use the default issue type for the project? 

Hi JD - Welcome to the Atlassian Community! Not sure that I have brain power for the full query right now but have you thought about implementing the board filter you have above? And then assuming that works, adding a quick filter to see if it filters out what you want. That way you could trouble shoot just that last part.

@Eric Barnes - Did this answer your question? 

@Bill Sheboy any thoughts?

Thanks to everyone for their effort. I have mostly been MIA for the last month as work and life have overwhelmed me. So glad to see the newcomers!!

Hi @Oliwia Poświat [Deviniti] Are we able to use custom fonts and custom colors? Or is there just a present list that is available? Also, is it just the top of the portal? Or does it go down to the portal issue view also?

Thanks @Simmo - This looks like it's going to add a lot of power. Are you some examples you can post either here or in the Automation playground that uses each of the new items in a more "realistic" example? (Now that you have done all of hard work, mate, you are probably bored and looking for something to do).

I would set up some type of rule on the AD side so that when the user is inactive you get an email or a notification to check that Group. Or you could even do a daily check as part of the Jira Admin responsibilities, though this would get cumbersome. 

Are they able to see it?

Hi @Gerardo Dalena - Any update?

Hi Kelley, I have not completely walked through every step- but no, that does not look out of line at all. And yes, with that many approvals, that could easily be what the workflow looks like. The big question is, Does it work? If yes, Great! If not, Bummer! But then where are you have problems?

The two would be under the main Help Desk page (more or less a tile) but there is not a level between them and main page. 

@Gyllchrist AGO - Avez-vous pu résoudre ce problème ?

Hi @SockBlocker - any update here?

Hi @Mike Bowen - any update? Did you ever solve it?

Hey Pete - so sorry for the delay, I have been very busy lately. I would add a Condition to check if the Issue Type = Sub-task (before the Edit Issue) Then add a branch after the condition for Parent Add Condition to check that all of the children are Done Then move the Edit issue under the branch. See the example here:

Hi Nada, So where are you with this? can you share the workflow and note which statuses have the approval attached. And then where are you experiencing your problems? Just the first problem first - let's take it in stages. 

If you edit the screen (the first option above), that might update them all. If not, you would have to copy your issue layout and apply it to the other projects. 

Go to Settings > Issues > Issue type hierarchy There you cand add levels.

Hi Tina - Welcome to the Atlassian Community! You can edit the screen used by the project and move the fields up on the screen. Go to Settings > Issues > Screens and search for the screen. Once there simply drag the fields up in the order. Or you can click the Configure button on the bottom right of the screen. There you…

Hi Casper, You do not have ability to control which standard issue types that a sub-task can be associated with. 

Conditions cannot be applied to the Create transition in a workflow. 

That should work - give it a try and see. 

Hi Jack, If you are using smart values in an automation rule it will look like this: To get the value of the parent:{{issue.fields.Cascade.value}} And for the child:{{issue.fields.Cascade.child.value}}

Since it is very random in nature, it would probably be best to open a support ticket with Atlassian to see if they can identify the source of the problem. Please post back here with the resolution when things get settled. Good luck! https://support.atlassian.com/contact/#/

Ah, thanks for the update. Unfortunately, boards for Team-managed projects are very limited and you are not able to update how the issues are displayed. You could create a second Jira Software board and link it to your Team-managed project to be able to do that if you like. Here is an article that will walk you through how…

Hi Santhosh, Yes, you can have non-agents be able to be Approvers and approve JSM issues.