John Funk Community Champion

I Nicolas - Welcome to the Atlassian Community! First, you CAN include a screenshot - click the camera icon. :-) Second, all cards/tickets/work in Jira are called issues. Things like Task, Story, Epic, etc. are issue types. Now, to make a field required you can do it a couple of different ways. One is to add a validator to…

Hi Marcel - Welcome to the Atlassian Community! This is a known bug that has recently appeared. You can follow the status and add that it affects your team using this link: https://jira.atlassian.com/browse/JRACLOUD-74554

Very cool! I think you will get a lot of use out of it. :-)

Hi Rosana, Yes, you can have a different workflow for every issue type in you the workflow scheme. And yes, it will require a migration when the new workflow is associated with an existing issue type. If an issue is in a status that does not existing in the new workflow it is moving to, the system will prompt you to decide…

Great! Glad I could help a little. :-)

Since you already have different transitions, just put the validator on the one for Developers 

The reason the Resolution field is empty is because you were not setting the value of the field when it was marked Done. If you followed the step by step instructions in the other post above then that problem is solved for the future. But it will not automatically update the existing issues that are already Done. To do…

Glad I could help a little!

So if you look at one of the Done issues - does the Resolution field have a value in it?

Hi Yafit - Welcome to the Atlassian Community! You need to add a post function to the transition to Done in your workflow that sets the value of the Resolution field. (Use the Update Issue Field post function). You can see more information in this previous post:…

Hi @sowjanya b , I don't know why they are excluded from the Field Configuration, but you can use a validator on the the Create transition of the workflow to make sure that fields are required. 

Just found out that this is a known bug that has recently appeared. You can follow the status and add that it affects your team using this link: https://jira.atlassian.com/browse/JRACLOUD-74554 You should both do that. :-)

The problem comes in that there is nothing in Jira that really captures the month by itself for an issue. So I have tried to solve this in the past by using two different methods. 1. One is create a custom field called Month or Month Created. Something like that. Just a simple one line text field. Then I create an…

Hi Yaniv (and Gail): Using the Issue Layout functionality you have in your screenshot above is specifically implemented so that it can be changed for one project only. Even though the same screen scheme is used by multiple projects. To change the screen for all projects that use that scheme, you have to change the screen…

@John Edwards - Just checking in on this one. Any update?

Hi Thomas - Welcome to the Atlassian Community! I am not sure that I completely following what you have setup and what you are trying to accomplish. So I have some questions first. 1. Is this a Next-gen project or a Classic Software project? 2. Why are you using Sub-tasks under an Epic and not Stories or other similar task…

Hi and Welcome Hunter! We are glad you are here!

I don't think you are going to be able hide the comments on an issue. Not sure why it would matter if the testers see the comments or know how long development takes (they would be able to see that in the history, which you can't hide either). The only way to achieve what you want is to spinoff a new issue for the testers…

Brilliant!

Let us know here how it goes. :-)

Hi @shasson24 - The columns that appear on the "Next" page are based on the filter you are coming from. As Bill said, if you want different columns to show up on the "Next" page, then you need to adjust the columns on the filter page you are coming from. 

Hi Michael, It tends to default to the last project you were performing actions on. Maybe go to your normal board for your project and move a test card or some other card.

Hi Cory, When you say you can’t find them - where are you looking? Have you run a filter such as: Project = ABC You should see all of the issues there and their statuses. If not seeing on the board then it’s probably the result of the board filter or a sub-filter on the board. Take a look there under Board Settings >…

Hi Lois - Welcome to the Atlassian Community! it is called the key.

No, the history table is not available to pull that information into JQL. 

What were you doing when you got the error? Here is a better guide to get to Automation For Jira * Go to Project Settings > Project Automation (on left-hand menu) * Press Create Rule in top-right corner * Select the Trigger "Scheduled" and press Save * Next Select to add an Action, and choose "Edit Issue" * Select the…

Was just thinking the that key represents the order they were created. I have to confess, I don't under the whole ranking business and how that is done by the system. Keys I know! :-)

Hi Fernanda - Welcome to the Atlassian Community! Can you give us a little more information of exactly what you would like to see? Maybe an example? Do you want to see all of the statuses an issue was in during a particular month? Or what month a particular status is in?

Hi Nagendra, You should be able to look at the history of the issue and see that latest changes and who performed those. 

Haven't tried this either, but maybe the JQL would look like: issuetype = Sub-task ORDER by key Try that out in the advanced filter section first to see results