My dashboard does not show the issues assigned to me even though I have some. How do I fix that?

[Andre Vignos]

My dashboard does not show the issues assigned to me even though I have some. How do I fix that?

[Olya Dayneko]

This also happened to me. I think it's about jira updates rather than resolution field. I used to see a lot of useful info in the dashboard and now i only see the issues i worked on.

[Nic Brough -Adaptavist-]

No, this one was definitely about resolution.  It was being set, so the gadgets that work off "resolution is set means the issue needs no more work" were hiding them.

[Nic Brough -Adaptavist-]

Establish why they're not appearing first. Find an issue that you think should appear, and check

• it is definitely assigned to you
• it is unresolved

If it matches both of those, then we may need to dig further.

[Andre Vignos]

Is there any way I can talk live to you? This behavior changed, it worked at first but no longer works. There have been no changes on my side that I can point to as causing the change

[Andre Vignos]

Is there any way I can talk live to you? This behavior changed, it worked at first but no longer works. There have been no changes on my side that I can point to as causing the change

[Andre Vignos]

My dashboard pie charts also don't work right. They are using old information and I can't find a way of getting them to use current information. Deleating and recreating did not help

[Andre Vignos]

My dashboard pie charts also don't work right. They are using old information and I can't find a way of getting them to use current information. Deleating and recreating did not help

[Andre Vignos]

Is there a dial in phone number I can call into?

[Nic Brough -Adaptavist-]

Er, we're not support, we're a community of users who try to help each other.

It sounds to me like your indexing is not functioning, but that would be very unusual for OnDemand (because you can't really install anything that might be breaking it)

Could you confirm if you are using OnDemand or your own installation?

[Nic Brough -Adaptavist-]

Ok, OnDemand. Can you try an advanced filter for us - type in simply "resolution = unresolved and assignee = currentuser()"

What does that pull back?

[Andre Vignos]

I used a corporate JIRA system at my last company and when I started my new job at a small company I found that they had no issue tracking system. A member of upper managment had been pushing for it and suggested JIRA OnDemand. I ended up being the administrator even though I am a hardware verification person. I have set everything up so I know everything about our setup

[Andre Vignos]

If I create a basic filter in the project for issues assigned to me it works. It is the dashboard version that seems to be messed up

[Andre Vignos]

How do I change the generic filter that the dashboard uses for "assigned to me"?

[Andre Vignos]

I figured it out. It is due to the resolution bug that exists in OnDemand. I could not modify that field at all. I was told it was a bug and as a result a JIRA support person forced a change to make it so i could. After that I created a new resolution called undetermined which is what all my open issues are set to.

[Andre Vignos]

When I create an issues the resolution is a required field. That is why I added undetermined. I tried to change it so it was only required when I closed the bug and was told I couldn't do that

[Nic Brough -Adaptavist-]

That doesn't sound like a bug to me, it sounds like you have set up resolution incorrectly.

The whole of Jira assumes that if you have a resolution set to ANYTHING AT ALL, then the issue is RESOLVED and hence will NOT appear in "assigned to me".

If you add a resolution called "undetermined" (or "unresolved"), then you are telling Jira that the issue is RESOLVED becuase there is something in the field.

You should immediately remove this "undetermined" resolution. The resolution field MUST be left empty for Jira to see the issue as unresolved.

[Andre Vignos]

Do you know if there is anyway of talking to someone in person to resolve these issues? I am wasting huge amounts of time and begining to question weather our company should continue with this product

[Nic Brough -Adaptavist-]

It's not required, it's defaulted because it's supposed to be used later in the workflow.

You must remove the field from the create screen you added it to, and delete any spurious resolutions. from the list because they are breaking your system.

(Sorry, I failed to answer your question about filters - the answer there is "you need to rewrite the whole of Jira's handling of the resolution field". OR just configure it correctly)

[Nic Brough -Adaptavist-]

As you have OnDemand, you have access to support. They may be willing to talk to you direct, but I've not tried it.

The resolution for these issues is quite clear though - you should use Jira as it's been designed and built, with an understanding of how it works. Remove the resolution field from all edit screens except those used on a resolve/close transition, and then delete the resolution options that are breaking Jira for you.

How it's been designed and why it does it that way is a different conversation (I believe the way the resolution field affects the open/closed state of an issue is very weak. It's certainly not intuitive, as you can see it's lead you in completely the wrong direction and broken your setup)

[Andre Vignos]

I wish I could remove the resolution field from all states but I can't. I complained about this and was told it was a bug. It requires we to give one with every state change

[Andre Vignos]

Originally I had no way of defining the resolution state when I closed the issue so I submitted a ticket and they told me it was a bug. As a workaround they changed my database in some way so I could do it. The result was that I had to give a resolution with every state change. I complained about that and they said there was nothing they could do. Now I am stuck

[Nic Brough -Adaptavist-]

I don't quite understand what that means.

Resolution is a field on an issue, which draws its possible values from a list. It doesn't belong to a "state" (and I'm not even sure what you mean by state, although I'm guessing it's "status"?)

You have accidentally configured Jira to set it when you didn't intend to, and also added a value to the list that you don't actually want to use.

To prevent more bad data being put in, you need to remove the field from all the screens that let you set it, EXCEPT the screens which are on the transitions that go into a resolved or closed status.

To fix your existing data, first delete the problem entries from the list ("undetermined" and any others you've added that are supposed to mean "unresolved"). The difficult bit is going to be undoing the damage to issues that you've got other resolutions that you still need on them, but are still "open". These will gradually drift into being correct if you do nothing because you'll working on getting them to a closed status anyway.

[Dave]

Hi Andre,

To clarify what was done in your support ticket - you wanted to configure resolution on a ticket but could not because it was not on your default screen. This was not a bug, the support engineer simply added it to that screen for you.

Additionally, you wanted to determine whether or not the resolution showed on a screen based on a workflow status, which is not possible or how that works.

Hopefully that makes a bit more sense!

Cheers,

-dave

[Andre Vignos]

I guess we are going in circles. Then I change states (for example from open to confirmed) it forces we to enter a resolution. Fixed was the default so I added undetermined because none of the resolutions available were applicable at that point. I tried to modify the configuration so I did not have to define a resolution till the closed state and it would not let me. I am forced to pick a resolution!!

[Dave]

That is because resolution is a required field and you have configured that screen to have resolution on it.

[Nic Brough -Adaptavist-]

I do understand why you think you're going in circles, and I think there's one thing missing from what we've said above, but you are close.

You need to do what I've said above, to repeat it

• Do NOT put resolution on any create or edit screen. You obviously have it on the screen you are using from "open to confirmed". Remove it from that screen.
• Do NOT try to have any resolutions that mean "unresolved". Only <null> is "unresolved"
• And the bit I think we have not covered - if you want to change the resolution on a resolved or closed issue (which I think is what you originally wanted to do, and ended up with a broken configuration), then create a completely new screen called something like "edit resolution", put the resolution on it, and then edit your workflow, putting a transition from "closed" to "closed" and/or "resolved" to "resolved", and use that screen on it. You'll then be able to change a resolution by using that transition.