Comments
-
A couple of options: * OOTB - Manual - Free - create a filter that returns all issues that have a release version but not in the desired status (e.g. Done) and perform a bulk update and transition them * Addon - Automated - $ - use and automation addon (automation for jira, scriptrunner, power scripts, etc) and when the…
-
It is a common misunderstanding for sure. In any event everything should clear once sprint 2 is completed.
-
Not within Jira itself But you can certainly zoom out in your browser. For example in Mac OS use CMD “-“ for out and CMD “+” for in and CND “0” to return to original.
-
In Cloud go to the General tab in board settings. Click on the administrator entry and add the user.
-
Was the sprint 1 board misconfigured which cause the done issue to roll into sprint 2? If so have you corrected the configuration so that Done is in right-most column? if so I would simply wait until sprint 2 is completed at which point they would disappear.
-
Hi Mark, I assume you are aware of this site? https://www.atlassian.com/partners
-
Is it possible that the issue created is in an unmapped status? Board settings > columns...any unmapped statuses?
-
If you are referring to how done issues are aged off the board after 14d, at this time this is not configurable.
-
First you need to ensure Done is the right-most column when you complete the sprint. Stated differently all issues in the right-most column should be removed from the board when you successfully complete the sprint.
-
the filter is returning issues that contain the selected labels. However, some of the issues also include other labels. When you use the pie-chart and choose labels as the metric all labels associated w/ the issues returned by your filter will be included. You can't exclude the other labels. I hope this makes sense but if…
-
unfortunately not. It would be nice if the project list could be sorted by popularity (most active to least active).
-
Yes the issue filter and subscription are intended for use by agents and collaborators. Customers only have access to the portal for viewing issues. I’m not sure why they need an email with links when simply logging into the portal to view open issues should suffice. If they are looking for an email as a reminder you could…
-
It looks to be a font or translation issue. Have you tried another browser?
-
This functionality is not available natively.
-
Hi Brian and thanks for the response. To be clear here I don’t work for Atlassian. I’m a user like yourself so can’t answer as to Atlassian’s strategy. One thing I will point out is that Atlassian has just announced they were acquiring the developer of Automation for Jira. I can’t say if they intend to integrate this or…
-
yikes! 100 future sprints? If you do not care to retain the sprints, and IMO should not but that is just MO, I would consider using bulk edit and clear the Sprint field for all issues in backlog. Now, I don't know how many issues that will leave in your backlog and how much it will help w/ loading of the backlog but it…
-
FWIW, what I do is to create a "customer test account" using a gmail account. I also test on a separate device so that browser caching and switching back and forth don't get in the way.
-
@Brian Spears, unsure why you have chosen to ask this here rather than a new post. That being said, as you have seen changing the issue type isn't in the native automation. You could consider an addon. For example I know that Automation for Jira provides the ability to edit the issue type. Footnote - this will only be…
-
quite a few addon options you might look at - Automation for Jira, Scriptrunner, Power Scripts, etc.
-
* Reports * Add new report * enter name of report * add series * select the flavor of TTFR metric (there are 4 to choose from) * Add Note you can add multiple metrics to the report.
-
unfortunately, as I stated in the beginning, it appears that indeed this workaround is no longer working. :-( I don't know of any way to do this at this point.
-
i'm truly baffled at the moment. something obvious we are missing or a nasty bug. Random thoughts: * inspect several of the "disappearing issues" closely to see if there is something unique w/ them vs. the "always visible" issues. Maybe there is something that will expose a clue here. * build a completely new board to…
-
I assume you saw this thread - How-to-display-date-and-time-on-Service-Desk-queue and deemed it unacceptable?
-
you may want to report the Chrome issue to Atlassian Support.
-
consider an addon, e.g. Scriptrunner, Automation for Jira, Power Scripts, etc. especially if you already have a suitable addon installed.
-
Absolutely! You simply need to construct the board's filter to include/exclude the issues you want. Without know exactly how you are setup today I can't give you exact directions but can offer food for thought. Let's assume your clients are associated w/ separate projects and you have development tasks and Marcom tasks in…
-
Par "méthode", entendez-vous les meilleures pratiques ou voulez-vous dire comment créer le tableau Kanban? En supposant que l'ancien ... Personnellement, je n'utilise pas le kanban pour mes projets JSD en général. J'ai utilisé le concept très tôt, mais les files d'attente fonctionnaient bien pour l'équipe. La meilleure…
-
The Time to First Response "gadget" on the dashboard is not specific to JSD and not controlled by the JSD SLA Calendar. You might consider setting up a TTFR report as an alternative.
-
Keyla, in reviewing your list it doesn’t appear to me that these individual items are actually addons. Can you elaborate on what you need? Ultimately, as Avinash stated you should speak to your Jira administrator.
-
Here are my first thoughts on the possibilities: * the user is a member of a group or role that is setup to receive notifications (project settings > notifications). Not likely if the are not receiving for all issues but still something to look at. * the user is a watcher for the issues they are getting notified on *…