John Funk Community Champion

Hi Jaime, Try adding a New Action for Re-fetch issue before the Branch.

To me it all depends on your Permission Scheme and what is granted to each role.

Hey Lisy, Check the context for the custom fields to make sure they include Epic issue types.

Hi Ayelet, You would need to incorporate a series of Conditions to check check if each field is empty. 

Hi @M_ Burger - Welcome to the Atlassian Community! After following that guidance, what problem are you still having? 

So you want to add another condition after the first condition for when the Severity Timestamp is empty. Correct? But you don't see that field in the list? 

Hi Sigrid, Maybe you could add a Condition before the transition to check for the same type of conditions you have on the two different transitions to B.

Hi Arnold - Welcome to the Atlassian Community! You will need an add-on to do that - something like ScriptRunner Behaviours or ProForma Forms. 

Hi Nofar, Can you share the rule that you have so far? 

Hi Aaron - Welcome to the Atlassian Community! Unfortunately, this is not currently possible. If you would like to vote for and follow the feature request, you can do that here: https://jira.atlassian.com/browse/JSDCLOUD-93

Can you share a screenshot of the settings page where you have dragged it below the Description field? Something like:

Some of the standard systems fields come built in to do that. That's why I think you need to copy the value of the contractNo field into the Remarks or Description field that supports the search. 

No worries about not showing the data - that is expected. I would try to do it with an automation rule, and after you clear the field, I would do a New Action, Re-fetch issue data. Then hopefully when it runs, if it does not update the field you might get some hints in the Audit log for the rule. 

Sie können das kostenlose Automation For Jira-Tool verwenden, das mit Jira Cloud geliefert wird. Ich bin mir nicht sicher, was Sie unter erneuter Einreichung verstehen, aber das ist wahrscheinlich nur eine Statusänderung. Zumindest können Sie dem Benutzer eine E-Mail senden. Hier sind einige Informationen, die Ihnen den…

Hello and Welcome, Brian! We are glad you are here!! Although I don't work with Bitbucket (we use GitHub), I am confident some really smart and compassionate Community Leaders will jump to the rescue. Just remember to be patient with us as well as we are only users like yourself, but enjoy helping where we can. I am…

Hi Scott, Can you share an example of the JQL query along with the results where it is not returning correctly? 

I am glad this started working for you. I hate that it was a frustrating process to get to that point. Always happy to help with what I can. 

Click on the Gear icon by your avatar in the upper right hand side of the top navigation bar. 

Can you get to Settings > User Management?

Hopefully, they will get to the bottom of it. 

Whoever set it up for you. 

These look like the same fields for both. 

Then you are not a Jira Administrator. That person would need to grant you permissions to create projects. 

Okay, one more question - can you click on Request Types, then select the Change request type. On the next screen can you do a screen capture? Should look like this:

So it sounds like you can create the new Project. Then create all new Epics under that project. Then you need to create a board that shows all Epics across all 6 projects. Correct? 

So if you go to Project Settings for the JSD Project, and then click on Issue Types, do you see the screen scheme linked to the Issue type? Then if you click on Request Types, and select one of the Request Types, and then Click on the Request Form - do you see the right fields? 

Hi @mf - Welcome to the Atlassian Community! Can you provide some more details about the "script"? Are you using an Automation For Jira rule? A ScriptRunner script? Etc. Where is the "script" placed? Can you share it? 

Hi JD, I have not seen that - or tried that. I would suggest you put in a Support Ticket with Atlassian to see if they can duplicate it. https://support.atlassian.com/contact/#/

Hi Dionei, For me, Story is too generic. We have lots of different Issue Types that are more descriptive of the work that we do. That way we can track lead time by work item type (issue type) instead of saying everything is a Story. We also due straight Kanban and not Scrum, so that might make a difference for some people. 

Hi Tom - Welcome to the Atlassian Community! You will need to be a Jira Administrator to be able to create projects. Can you get to Settings > System?