Comments
-
The add-ons provide different frameworks for hooking into the data you're working with. In a Scriptrunner scripted field, you don't need to mess around with issueimpls or building issue structures, and you don't need to do much with custom fields - the issue object is immediately available along with all its imports. def…
-
If you create the board with a filter that's a bit too complex or open, it can give up and just show you every single status there is on the list. And, annoyingly, you can't get rid of them easily, even by correcting the filter to narrow it down to the project/issue-type you actually care about. I've never worked out an…
-
You're right, if you insist on using a status of "won't do". Next-gen expects you to include that in "definition of done", meaning the done column, but does not yet allow you to map multiple status into a column like classic does. Your options are to use a classic board with "won't do" as a status in the done column, or,…
-
Be aware that going a lot over 1,000 will kill your Jira - performance will degrade and it will eventually crash. The solution most people use is reporting tools inside or alongside Jira - apps to do their reports directly, or apps like EasyBI or Dataplane which understand the data far better than an extract will.
-
An issue that is in the "done" column is done and needs no more work. Core Jira (without Software) has a different concept of "done" which is simply "the resolution is set". Historically, there's been a long and often painful disconnect between "done" and "resolved". Next-gen fixes that by combining them and binding the…
-
You have to use a Jira project - Service Desk is not separate, it's a layer on top of a project that simplifies things for the end-user ("customer") and adds reporting and other functions for the people handling the requests ("Agents"). The Agent still uses the jira project to handle it all in whatever level of complexity…
-
No. The REST interface is (now) an integral part of Jira, and hence part of the core offering! It's *always* available now.
-
I'm afraid this is just a front-end report of something going badly wrong on the back end. You'll need to read the application log (<jira home>/logs/atlassian-jira.log) to see what the underlying error is.
-
@Thomas Deiler- that's why I tend to use "Scripting or automation tools". My sales guys would love me to heavily plug SR all the time, but I try to stick to what Alexey has done here - a working example. If I don't have the example to hand, a non-advert generalisation is better. (If I must... SR has two ways to do this. A…
-
The problem is that there are many ways to do this, and Atlassian can't document how you do it (because they don't know). Where did you install Jira? Start there - the scripts are under <jira install>/bin and you'll be able to locate the data directory by reading <jira install>/<jira…
-
This is a 7 year old conversation. It's not quite accurate any more. I see you've asked this elsewhere, so I'll not repeat the answers there!
-
Ok, from my standard copy-and-paste for transition validator and screen: * one of your admins has placed a "validator" on the transition that makes the comment required during the transition * one of your admins has removed the transition screen from the transition (probably a different admin), or the workflow was designed…
-
Yes, the common-sense way to do it is not allowing delete. Because the issues simply go, if you need any of the data, you're stuffed. I do agree this is a weakness in many ways, but on the other hand, if you're deleting at this level, you should be doing it because you really don't want it there, in which case the…
-
Rank is a semi-hidden field (the contents are not human friendly) which you can use for ordering in filters. It's not really an absolute value, it's a relational pointer. You "edit" it by moving issues relative to each other. The order you see sub-tasks in on a parent is still ranked, but it's local to the parent issue, it…
-
Sub-tasks are separate issues, just they are tied back into their parent, displayed as part of it, but still individual entities in their own right. I'm not sure what you're looking for Jira to do here?
-
It's a nice idea for a badge, but I foresee one significant problem - most bug reports are duplicates, and Atlassian are trying to cur down on duplicates by discouraging these. Naturally, I suspect the best idea would only to grant badges to people who report new bugs, but then we'd need a mechanism to grant badges when…
-
Oh, and my mathematics failed me too - it's not 11 hour 49 minutes, it's 10 hours 51 minutes, i.e. 651 minutes, so I'd say the -652 you're getting is right, as I assume there will be a few seconds to round it up to 652.
-
What does the bamboo log say the error is?
-
It means the value in one part of a field "cascades" down into limiting the list in another. Country/region is an example - the value USA in one field would limit the region list to the 50 states, but if you selected UK, you would probably find either England/Northern Ireland/Scotland/Wales (and then possibly protectorates…
-
Yes and no. "Issue key" is usually just called "key" by most of us. Rank is the order in which you have placed a set of issues, it has nothing to do with the key.
-
Yes, you're misreading the times. 12:34 pm is almost 11 hours before 11:25pm, (pm = post meridian = after noon) so 11:25pm is the larger number.
-
You will need to talk to the people who are providing your Digital Signature service. We're a community of users of Atlassian Software, none of which are a Digital Signature service (Although they can carry signatures of course)
-
You need to edit the permission schemes for each project, as described above. The admins are getting "browse" somehow (usually you will find someone has granted "browse project" for the administrator group)
-
We can't help you with your systems authorisations, it's nothing to do with Confluence directly. Confluence is using another system for authentication, and you need help with that (unless you have system access to Confluence and simply wish to switch it off for all users and use a plain login) You will need to talk to the…
-
So you're not using time-tracking for any form of timesheeting at all? It looks like your date/time might be coming from Tempo, where I seem to remember you can configure your working day with start and end times. Should be able to set that to midnight/midnight to get the whole day.
-
The number looks wrong to me, as the 11 hour 49 minute difference is 709 minutes, but the negative sign is right - you're taking a larger number away from a smaller one.
-
That's wrong. A "superuser" may well have complete admin rights, but that is admin rights. I've looked after Jira systems where I can only see a fraction of 1% of the issues in it, despite being a "superuser". The statement "the `superuser` is executing the queries. So every entity is visible to the query" is completely…
-
The data will be retained in full. For the changes, have a skim the release notes for Jira 7.2, 7.3 etc through to 8.0.
-
Not sure what a "condo" is, but if it means what I think it does (a US-English contraction of "condominium"?) , then I've come close, using Jira to handle buildings maintenance in an office. That project went so well, one of the clients users adopted Jira to do buildings maintenance on some serviced flats, and another on…
-
There is no rollback in the software, you will have to restore from the backup you took before doing the upgrade.