Jack Brickey Expert

You can certainly add them as a watcher which will accomplish your goal. Now the user will still have browse permissions to other issues can could find/view them if the wished.

It remembers where you were last. If you were in queues and the exit to another project for instance and come back to the previous project it should return to where you were last. If you were in queues it should return there. At least that has been my observation 

Add the approver as a Watcher. This can be done manually or use an automation addon to add once approved. If the approver is static you could add the, wine created.

Try this. * create and save a filter like this - project = myproject and labels in (a,b,d,r) * add a pie chart gadget and reference the saved filter and use labels as the metric. your idea of a monthly view pie chart doesn’t work. Consider using the created vs resolved or a bar chart. That has time as the x-axis

You need to set the permissions for “Manage Sprints” to meet your needs.

I will provide detail from cloud perspective. I believe it is similar in server at least such that you should be able to find. First you need to be an admin. Go to Jira settings > system > shared items > dashboards. Find the dashboard in question and to the right click on the ellipses and delete.

Are we talking Jira or Jira Service Desk here. I assume Jira since that is where you posted but there really isn't a notion of "Customers" in JSW as there is in JSD. In Jira, if you want someone to have access to the application you must add them as a user and you can restrict their access at the project level (or beyond…

can you share a screenshot of what you are seeing/not seeing?

further on what Joe is getting at here. If you have an actual Status that is named "Closed" and it is showing in your above filter results, something is very strange indeed. However, if by "closed" you are referring to an issue you believe to be closed by some means (resolution value, column on kanban, etc) but the actual…

@Chuck Foster , I noted a lot of recent posts by you on the classy roadmap topic. I thought I would point out the following guidelines for vendor related posting. One key thing to avoid is redirecting folks off-Community to other vendor solutions. It is fine to share your opinion/recommendation. Of course if you were to…

it sounds like you want to be able to dynamically give browse permission to an individual user only when they are @mentioned and only to the one issue. That is not possible.

so you are saying that some issues returned by that filter have a Status other than "Created"? That seems very odd unless of course you have a secondary custom Status field which would be bad. 

a fix is being rolled out so stay tuned and keep trying.

you can view the history for individual issues under the History 'tab'

The health gadget considers done to be any issues in the far right column of the scrum board. So if you place the ready for production status into that column it will count as done in the gadget. 

To be clear here you don’t have two RB swim lanes? The next thing I would do is click on each RB icon and assess the issues shown for each to understand if they are indeed assigned to the exact same user. Also, inspect the RB user(s) in User management under Jira settings. If everything looks copasetic I would contact…

If you simply want to occasionally look at this info you can look at the history info. If you want to monitor or report on this use an addon like Ravi mentioned. 

One thought comes to mind using an addon for automation or scripting... create a status, say “approval assessment” with a single transition “approval”. The user transitions the issue to this status. Using the addon, trigger a rule that when transitioned into this status the next transition is done based upon the value.…

Please share the article you are viewing. I expect you will need an addon but that depends on your exact requirements. have a look at the Tempo addon or similar resource calendar addons

Add this to your query updated < -3d 

This is a known and highly reported issue in the last 24hrs. Hopefully atlassian will address soon.

You must ensure that the Resolution is set when moving an issue to Done. Otherwise it is not considered done in the eyes of Jira scrum. You can either use a Post function on the transition to set it or you can use a screen to require the user to set during transition.

Yep it has been reported and I hope to hear back from them with a positive response.

Yes this has been reported earlier and I am hopeful it will get addressed.

Are you confident that you don’t have two RB users. It would be interesting to do swimlanes by Assignee.

If you want them to use the “+” to create issue instead of the raise request then be sure to set the request type when doing so.

Yes there is at least 5 posts on this today now. I have submitted a ticket and suggest others do as well.

This is the fourth post on this today. I have reported it to Atlassian and hope to see it reinstated.

This has been reported on a couple of other posts today. I have confirmed it and opened a Support ticket with Atlassian. You might wish to submit feedback on the need for this to be reinstated.

another thread