Jack Brickey Expert

that is certainly unusual so i suspect something in your instance. Please post the final result here to close the thread out.

@Prashant, a board is simply a 'filtered' view of issues. The issues that are displayed are governed first by the primary board filter (board setting > general) and any temporary quick filters you might create (board settings > quick filters). So if you don't want issues of certain conditions to be displayed on a board you…

ok so you should see something like below on your kanban board. Other questions/things to try: * what do other users see? * has this suddenly stopped working * log out and back in * clear cache on browser (most issues seen like you are indicating are correct by doing this) * contact Atlassian Support

@Ana Narváez Vila, are you on cloud using the new UI? If so please check that the sidebar is not simply collapsed. Can you send a screenshot of what you are seeing? Can you try another browser and/or clear cache on current browser?

No problem Jimbo. The Community (represented by this thread) is a group of users much like yourself. Atlassian sponsors and monitors/moderates the Community but only occasionally jumps in often time driven by requests from community champions. There is a dedicated support page where you can submit believed to be bugs or…

@boardtc, this is a different issue and you should create a new thread but the short answer is that you need to require the Resolution in the transition to Done status. There are quite a few threads that provide the detail on how this is done. 

Hi @Adrian Rawlins. You could do one of the following: * manually have agents move the issue to the new issue type that has the different WF. * incorporate the different WF considerations into the existent WF * use an addon, e.g. scriptrunner or power scripts to automate moving the issue to the new issue type

I would suggest reading this article to see if it helps you. Basically you should create an SLA for "Time to First Response" w/ the metrics you require and then create a report to monitor performance to your SLA goals. you can also see TTFR in an issue filter by adding the column to your report. There are some other…

@James H, this is an old thread. If you want the time displayed I would suggest you submit a Suggestion to Atlassian. It won't get much attention here.

Yes. Make the change and publish. You will need to add the All transition to Done first. 

That isn’t the workflow we worked out. you should have the one without any transitions between the statuses. Rather the one that has “All” to each status. This allows you to transition an issue from ANY status to any other status. The one you show above would only allow you to move to Done from Test since there is only one…

This would be odd. First verify the active workflow for WOR-130. Go into the view screen for tha issue and click on the view workflow link next to the status. If it is the same as the simplified WF then which statuses can it be transitioned to? Do other issues have the same problem?

If you go to a specific issue and click Edit, do you see original and remaining estimate fields? If not click the configure fields in the top right and search for it to see if it is configured to display. 

@Manal Ramsis, to be clear please confirm that the following is the issue at hand: * customer A sends an email to the helpdesk and CCs customer B * customer B responds to this original email; not the email response sent by JSD with the issuekey in the subject. In this case JSD can not distinguish between the two and has…

I think the issue here, and I think you already know this (?), is that there was not activity for Feb 4. No issues opened none closed. So the charts drop to 0. There is no “fix” because the chart is working as designed. So you can either accept the behavior or use a different chart that sort of reverses the logic showing…

You could consider using an attachment form. However if your customers are frustrated at the length of the questionnaire then I would revisit that and see if every question is absolutely required. 

@Anupam Poria, based on everything that has been stated above can you convey your specific issue? Are you attempting to delete and cannot? Are there any sprints active?

@Ian Johnsen, just one piece of advice here FWIW. The jqls are overly complex. I have a hard time just consuming. I would recommend creating a Group and placing the users in that group then manage additions and deletions in the group. As Brittany points out the question doesn’t clearly state your objective. Then again if…

Let me first state up front that I have not used constraints in some time so maybe something has changed. With that said.... no. The only thing constraints does is provide an alert in the way of color coding. 

maybe but lets have a look at your actual situation. Can you go into board setting and columns and capture the image and paste here?

try the following... (labels = A OR labels = B) AND Status not in (Completed, Closed)

you bet. please respond back here w/ final resolution.

i did a quick search and did not find one listed. while it is certainly possible that there is a bug it would surprise me to be honest. works fine for me in cloud. regardless i would contact atlassian if you believe you have done things correctly.

@Eleni Theodoridou, cloud or server version? Certainly the behavior is not correct. I understand why @Brittany Wispell asked the "update" question as your screen shot would indicate that you did not. If you still have "Update" showing to the Actions column of the field then please click it (again) and ensure it disappears.…

@Maurice Côté, this should not be the case. You may wish to look at this thread for more details on the designed behavior to assist w/ troubleshooting.

You can do this by clicking on the "Configure fields" button in the create screen (image you provided) and click custom. Check the fields you want. You can also do this by going to the project settings and edit the screen associated w/ Create.

If you add an Original Estimate the time tracking area will then display on the view issue screen. You can then log time using the “+” symbol on the top right of time tracking area. You can also do this via a board in the detail area and there are shortcut keys as well. If you didn’t add the OE at creation you need to Edit…

Let’s explore this a bit. I’m not sure what you mean by change request and change start date so the following may or may not be useful. If you have a statuses that reflects “approved” and “declined” you cold create an SLA for the issue to reach “approved” giving you the trigger for your desired decline action. Next you…

Note that you need to add the estimate at creation time or use the Edit function to add estimation to an existing issue. 

I assume you mean SLA? You do this within the Automation settings area. If you have a current rule to notify on SLA breach you can add a Then action to send an email to any Jira user.