John Funk Community Champion

Does it still give you the pop-up screen? With those same options?

It will stay open until you mark it with the Accept answer. ;-)

Hi Vesa - Welcome to the Atlassian Community! You should find lots of people here that are willing to help. :-) Is there anything in particular right now?

Hi Jim, I am pretty sure that when you create a Classic Software project that it creates a Bug screen with it. Maybe even a Bug workflow. I haven't created a project from scratch in a while. I will say that we have different workflows for Bugs, Defects and Software Engineering issue types in our workflow scheme.

I would change the If: Sub-tasks match status = "Done" OR status = "Abandoned" to just say If: Sub-tasks match status = "Done" as a test and see if the screen shows up. 

1. It is the initial workflow created with the Project. It will have the name Simplified in it. 2. Only for Simplified workflows My best suggestion to you is to have a project Admin try it to verify. Not someone who is a Jira Admin, but just a Project Admin. And only on a problem that has a Simplified workflow. 

Go to Settings > Issues > Field Configurations When you get to the list, simply click on Copy for the FC you want to copy. 

I don't think the screen is coming from Automation for Jira. Your rule is to fire when the Sub-task is marked Done. But the screen is getting in the way of the Automation finishing which says to make the Parent Done. If you are doing that through Automation, you shouldn't be asking where the parent should go - the…

Project Admins can only do it for Simplified workflows.

Hi Manoj, This seems like it is more of an education issue that a system issue. It should be your process that if you have been on the page for a while and haven't refreshed that you should do that before updating any fields, including Assignee, if you are in an environment where multiple people are potentially working on…

Hi Yuliia, This is a function that is coming soon to Next-gen projects. See the Easy clean up your board section in this roadmap article: https://www.atlassian.com/software/jira/whats-new/next-gen?_ga=2.104316484.513035551.1586779195-1313086432.1576012938#intheworks Also, see the comments in this previous post:…

Can you share a screenshot of your rule? What is the first step in the rule? What causes it to fire?

Hi Rupa - Welcome to the Atlassian Community! I guess my first question is why are you doing releases for issues that have not been marked Done yet? That seems to be a flaw in the process. If the release will mark the issues Done, why haven't they been marked Done already? And then release the Done ones? Having said that,…

They should be able to see them, yes, because they can modify the workflow. However, you really shouldn't be modifying Simplified workflows. If you need something more then you should create a copy and modify that. But only Jira Admins can do that. 

Can you click on the Accept answer button above to close this one out? Thanks!

I am glad you were able to track it down. :-)

Hi Flo - Welcome to the Atlassian Community! You actually modify the Field Configuration for the Issue Type in question. Or all of them under the Field Configuration Scheme. The Scheme is actually just a collection of the Field Configurations. See the document that Bibek shared above for details and post back here if you…

Hi Roja, Project Administrators would be able to see for Simplified Workflows for their project only. But outside of that, no one other than Jira Administrators (i.e. systems administrators) can see all of the information about transition details. 

Hi Todd, If you are using Automation for Jira you can use this: {{issue.Created.convertToTimeZone("America/Chicago").longDateTime}} Just change for your Time Zone if need be. 

:-)

Hi Robert - Welcome to the Atlassian Community! Here is what I did. 1. I created a new filter with: fixVersion is not EMPTY AND statusCategory != Done 2. I created a new dashboard (or added a gadget to an existing dashboard) with the Issue Statistics gadget 3. I used the filter I created in 1. and used and a Statistics…

Hey @Yoda - Did you get this resolved?

I have not tried that before, but you could probably setup an Automation For Jira rule to Edit the issue and populate the field when an Issue is Created. 

You should probably put in support ticket with Atlassian then as they would have access to your instance. You can do that here: https://support.atlassian.com/contact/#/ Then please come back here to update with the resolution. 

@Jason Wong - Thanks for clarifying. But how do you guide the user when they are using those fields in some type of automation? There will be MULTIPLE fields with the exact same name. How will they know which one to use? 

Hi Christine - Welcome to the Atlassian Community! A question first - Why are you copying the Epic to another board? Are you really just wanting to show the same Epic on two boards? Or is the Epic being copied to another project? 

Sure - you filter will look something like this: Project = ABC and Component = 123 for one board and Project = ABC and Component = 456 for another board and so on. 

Is there more than one business value captured in Epic B? If so, how will you link the hours in A to value in B?

Yes but what is the filter shared with? Please post a screen shot of what the shared filter has. It should look something like this:

Hi Claudio, Why is there a screen showing up when you click the Transition to Done? I don't know why the Cancel doesn't actually cancel the Transition, but it doesn't. So what we have done is to create a custom field of radio type with just simple Yes or No value. The field would actually same something like, Do you really…