John Funk Community Champion

Sorry, misread that. You will need to edit the screen itself to add the field. If you go to Project Settings, then select Screens. Once there, select the screen scheme and then the actual screen itself. Once there, you should be able to add the field to the screen. Let me know if you have problems with it. 

I am still unclear as to how a filter will show you problems with your structure. Can you be more specific?

Hi Kate - Welcome to the Community! Are they not displaying in the CSV in the same order they are in for your filter?

Hi Paul - Welcome to the Community! You should be able to simply drag the fields into the section you want them displayed. It's really up to you to decide where you want the custom fields displayed. Now, having said that, this applies only to the "new" JIRA Issue view and is not possible in the "old" JIRA issue view.

Hi Roland, Fields are not associated with a user. They are associated (Context) with projects and/or issue types and are visible on forms. So I guess you could trace back what fields are viewable by a user, but that would take quite a bit of work. What is it that you are really trying to accomplish?

Hi Valentine - Welcome to the Community! What specifically is your question? Or the problem you need help with? 

Great!

Hi and Welcome to the Community! You would need to modify the permissions for each of the filters to not share with Public - maybe some other internal group. 

Hi Gaurav - Welcome to the Community! Modify the filter for the new board to contain both projects. project in (project 1, project 2) That will show you all issues from both projects. 

Hi Eunice - Welcome to the Community! Can you provide a screenshot of the permissions page? Something like below. It is the permissions on the board filter that makes it visible to other people. 

Hi Alexis - Welcome to the Community! The screenshot you show only applies to the "new" JIRA issue view. If you are using the "old" JIRA Issue view, you will need to go to Configure Fields to make it show up when in Edit mode. I hope that helps!

Hey Katherine, Your workflow will have a transition to Done. Add a post function to the transition to Update issue field (not Update issue custom field). Then select the Resolution issue field and then select whichever value you want from the field value drop down. 

Hi John - Welcome to the Community! Certainly, you can do that. Just go to Board Settings, then choose Swimlanes. Then modify the JQL for the Swimlane for Epics to include something like issuetype = Epic and status != Done Let me know if you have problems with it. 

Hi Anthony, How did you create a task without field A being populated if it is required? I would imagine that what is happening is that the task form is being updated with the link to the Sub-task issue but it can't update because there is a required field. But that shouldn't be an issue if the task form requires field A…

Defects are a Sub-type for us. But Bugs are not. We would create them as Bugs if they are not directly associated with the stories in that Sprint. Does that make sense?

No worries - thanks for doing that!

Great! If that solved it for you, can you click the Accept Answer button so others will be able to see the resolution in the future? 

Hi Joanna - Welcome to the Community! Click on the maginying glass on the left nav (Cloud) or on top nav (Server). Select Advance search for Projects. You will arrive at a list of all Projects. Click on the Create Project button. You will then decide whether it is a Classic Project or a Next-gen Project. If you do not see…

I know it's a lot of steps, and I have, unfortunately, done it more than once during the Migration - it's easy not to notice that the statuses are changed. It's worse when they all default to Done instead of something less harmful like Backlog or In Progress. :-)

Hi Alison - Welcome to the Community! 1. For our process, any Defect that is not going to be immediately fixed is converted to a Bug issue type. (Which is not a Sub-task type for us, by the way). Our definition - Defect - identified during QA Testing and must be fixed now and code cannot be deployed until the Defect is…

Suspected as such. First, you need to modify the new work flow to add a transition from Done to Backlog. I would place a condition on that transition that can only be performed by a group - then choose Administrators. Also, make sure you add a post-function to clear the Resolution field. And maybe clear the Resolved field…

Hey Manuel - Welcome to the Community! Oftentimes when you move to a new workflow, the new workflow might not contain all of the statuses used by the previous workflow. In that case, JIRA will migrate from the old status to one of the statuses available in the new workflow. So, first, make sure that you have the Backlog…

Very good. :-)

Yes, Aha! is a good product. 

Can you mark this one as Answer Accepted so the question doesn't stay open? Thanks!

You should probably open a support ticket directly with Bob Swift then. :-)

Hey Brandy, If they have access to browse the project in the Permission Scheme, they should be able to run the reports. 

Hi Talha - Welcome to the Community! You would need to use a Marketplace App add-on such as Automation for JIRA or ScriptRunner or PowerScripts since it would be triggered by a field value change and not on a transition.

Hi Skylar - Welcome to the Community! Have you tried simply clicking on the issue and dragging the issue either higher or lower on the backlog? If it will not let you, make sure your underlying Filter for the board/sprint has Order by Rank on the end of it. 

Hi L Sloan, One way to do that is to create a base issue with the information you want and just leave it in your Backlog. Then simply clone that ticket when you need something new and change the values as needed. You can also incorporate post functions on the Create transition or other transistions in your workflow to…