Jack Brickey Expert

check the filter that defines the board (board settings > general). Determine all projects that are included in the board's filter then check to ensure you have Manage sprints permission for each project.

create this JQL - project = xxxxx and sprint in openSprints(), or similar. Save it and share it. On the dashboard add Filter results gadget (or gadget of your choice). Associate the filter to the gadget. The key here is openSprints() as it will stay current.

so let's try this... go to project > project settings > screens find the screen configuration associated w/ your issuetype and click on the pencil in the next screen click on the link displayed in the screen column make sure the field you want is in the list of fields, if not add it at the bottom go to project > project…

I think you want an Cascading select field that should meet your requirements

you can use the Ranking feature available in the board if on Classic projects. There is no real precedence-linking feature. You could create a custom field and number them but that can be an exercise in futility until you fully lock down the tasks. If you go the route of the later (not recommended) then leave space in your…

ah...so you want to distinguish 'scope churn'. So OOTB the solution isn't pretty, i.e. there is no JQL to show added after sprint start. However.... If you have Scriptrunner I understand they have this function - addedAfterSprintStart(board name, \[sprint name\]) With out Scriptrunner (or similar addon?) then consider…

Not sure I follow here but let me throw this out to get the discussion going. If you go to the portal and click on the "Requests" icon you will be taken to a screen where you can view your requests and filter them. On the top right header you have "Any request type" in a drop down. If you click on that the request types…

but isn't everything that shows on the active sprint board committed? in which case they would all be the same color. Can you explain your goal further so I might assist?

yes this will work. you will need to create your desired email and add the custom email to your Project settings > Email requests. Note, you will need a unique email for each JSD project. If you only have one project then you only have one incoming email requirement. Finally, note that the outbound email is still governed…

good catch Andrew! I did not catch that this was on-prem. :-(

please define "it" in "it is only happening...". What exactly are you doing here? Explain what is happening for other defects that is different.

Sadly no. Please see this issue that basically says the NG is the answer but that doesn't help JSD classic anyway. JRACLOUD-3821 

Ok so Process Status is some custom field you or someone has created in your instance. I don't know what it's purpose is but, unless you have some automation that triggers on the modification of Process Status to actually change the Status then they are completely decoupled. So if you wish to change the Status you must…

Yes please see this article - migrate-between-next-gen-and-classic-projects Understand that, how clean things go here will completely depend upon your current NG project and how you set up your Classic project that you move issues into. I would suggest setting up the Classic, creating a few test issues in the NG, move them…

Hi Nina, to satisfy my curiosity can you provide a screen shot of the following: Jira settings > Issues >Workflows and find the workflow that you are editing? Next, when you change a post function on one workflow have you actually gone in to view another workflow that represented an undesirable change? Have you done a…

Then you are using Next-gen project which changes things. Please verify this by looking to the bottom left and see if you see "You're in a next-gen project". Traditional workflows do not apply to NG projects where the workflows are inherently built in and created as you build your board. Given this, let me inquire into…

i need more info to assist here. Some questions/thoughts... * please view the Workflow to understand what transitions exist * are you able to transition issues? * what do you mean by "Progress status"? * you mention "Progress status" being set to "resolved". what does this mean? * are you saying that you cannot transition…

Based on what I read here I would say you have a shared workflow and that workflow has post functions and when edited then all projects/issuetypes sharing that workflow will be impacted. You will want to make a copy of the workflow and associate it to your desired project(s) and edit the post functions to meet your needs.

Go to project settings > issue types and ensure it is listed if not add it.

Go to the project where you wish to assign the workflow/scheme. Go to Project settings > workflows and click add workflow > existing workflow and find yours. Finally associate the workflow to whichever issuetypes you want.

Yes. Just follow the upgrade guide. I found this one from 7.13 to 8.5

Agents are added to projects. If they are not added they will not have access. You can go to Project settings > People and manage who has what sort of access.

Yes. This can be done by adding condition and/or validators to the transition in the workflow.

Yes the existing license remains.

Can you review the history or all tab to see if it provides a clue. Is there an entry that indicates the field’s value changed?

Keith, you have posted this in the Jira Software collection but I have a suspicion that maybe this is for Jira Service Desk given you are talking queues and Agents. Assuming so, please edit the queue where you are undesirably seeing closed issues. Inspect the JQL for the potential cause. My first thought was that the JQL…

This is not possible. You can have a unique assignee of course and you could create additional user picker fields for other purposes and associate to an epic if that helps,.

i just replied to another similar post. I seem to recall there was a recent bug that popped up on this. You might wish to reach out to Atlassian Support to ensure you are on the latest SW. I think it had to do w/ different domains but TBH I can't recall. Before troubleshooting you might check w/ support.

So it appears that you are on a Jira Software project not a JSD project. SLAs do not apply to JSW projects w/o some addon to offer such a solution.

I seem to recall there was a recent bug that popped up on this. You might wish to reach out to Atlassian Support to ensure you are on the latest SW.