Comments
-
Confluence backups are intended to be complete, capable of restoring an entire system. So they contain everything. (If you look carefully at the main database backup in each of them, you'll see the 26 has another day's worth of data in it) If you want incremental backups, you're going to have to build your own system to do…
-
The Atlassian stack can do a lot of stuff, but I would not recommend it for this sort of thing. You would be a lot better off finding software that is built for trip fare collection (then manage it using the Atlassian suite)
-
So you reverted to a copy of a working file and configured the right one to be deployed? Is that what you mean?
-
The resolved date is the date the resolution was last changed. It's calculated from that change.
-
Customer numbers are indeed unlimited. Which makes me suspect he's been added as a user somewhere. Check admin -> manage applications to see what groups have "can use x" and see if there are any accounts in those groups that should only be customers.
-
If you delete an issue, its attachments are killed off too, so yes, you will free up space. I'd recommend not deleting the issues though, as they're gone for good. I'd recommend only deleting the attachment, and leaving a comment like "attachment x deleted to recover space", so you keep the history of the issue.
-
Yes, you have to "pay". Each one of these dummy users will consume a licence, as they need to look like valid human-backed accounts in order to be used, irrespective of how minimal their interaction may be.
-
It works exactly as documented. What do you think is different?
-
I don't think you can - you don't have information stored as to who the lead should be for each project, so there's nothing to work with.
-
Ok, that tells us the problem is on the proxy, not the Jira connector. You'll need to look at how that is set up to proxy between Jira and the world.
-
Ok, ignore Behaviours. Insight can restrict the options offered by user. See https://documentation.mindville.com/insight/5.0/insight-administrator-s-guide/insight-custom-fields/insight-custom-field - jump to "5. You can restrict this custom field to just show JIRA User related objects" and read from there!
-
That's not right. An issue always has a key, they don't exist without them (or if they do, your database is fried). We need to see the Key of issue 10002.
-
I would guess that you have got the resolution on the transition screen and are setting it ro done in a post-function in the transition. The post-function is overriding what your people enter on screen as it happens after the screen.
-
With Jira Software, you have three levels of hierarchy, two of which are totally flexible on names. In Jira-speak, you have Epic -> Issue -> Sub-task. Epics are a single, one-off type - you can't have more than one issue type at this level and, at present, you should never rename Epic. Issues though, you can call them…
-
The easiest way to think of this is that "Status is not a field, so you can't edit it" Status is an indicator of where an issue is in the process. It's showing you an underlying property of and issue as it relates to the process (workflow) it is going through. To "edit" a status, you move it through the workflow using…
-
Are the issues in the last column on the board?
-
No. The mandatory flag is not set by screen, it is done by issue type and project (in the field configuration). The move function applies this flag when the target issue type needs it in order to avoid the data becoming inconsistent. Validators apply only to transitions. Edit and move are not transitions, so they don't…
-
What type of field is it? I can only think of a handful of fields that restrict the list of options in themselves by person, but they're all system fields, not custom fields. I therefore suspect you have an app providing a field that does some form of restriction by user. It might be an app providing modifiable fields, or…
-
I'm afraid this is not really something for Atlassian - you'll need to work out why your client can't reach the server. However, telnet port 443 "working" suggests that it may the browser rather than the networking. When you say "can't access", what errors are you seeing in the browser?
-
The exact answer is "no". You can't do this natively with Jira. It has no show/hide functionality in it. You have ruled out Behaviours, which is the only generalised way to add it to Jira, and there are a couple of other apps that provide fields that do things a bit like that. But for plain Jira, it is a simple "no". To…
-
Original estimate is a part of the "time tracking" field - you can add that to a screen.
-
Yes, a custom field copied to the assignee is the most simple and clear way to do this. Spot on! Issues in different projects are completely independent themselves. They may share common data (Links, Epics, selections in fields, etc), but updating one issue will have no effect on another (unless you've added code to do…
-
So why have you confused this with two projects and different people and stated that you want one issue? It now sounds like the talk of separate projects and people is irrelevant. Your need is "assign the current issue to the development lead when it goes to a certain status" You will need to use one of the automation or…
-
If you've got 24 done, you already have the "exact steps and commands", and they work. The question should be "what is different about this one?". Also, what are the warnings and errors you are seeing?
-
The message you have translated for usis saying that the person who cannot update the issue is not a Service Desk Agent - they are not in a group that grants them Service Desk Agent access. (Thank you for the translation, I'm afraid I only have one language)
-
This cannot be done (as described). An issue belongs to a single project, and, rightly, can only ever have one assignee. I suspect what you are trying to do is not have one issue. I suspect you want to clone an issue into a second project, and assign it to the other project lead. You will need to use one of the automation…
-
I think you have had no response because you have limited yourself to MPP and Ceptah Bridge. Why are you bothering with them? 100 Bugs in Excel is a doddle to save as CSV and import into Jira, no need for other software.
-
What errors are you getting? "I cannot change the workflow" and "choice of columns" are not telling us what the problems or errors are.
-
Because I am trying to help. I probably can solve your problem if you would give us the information we need, but we can't get far without it. If you need support, please see the original answer on this question. Bear in mind they will ask you the same questions that you are ignoring here.
-
Er, don't put secure information into the Welcome or Text gadgets? That can't be hard.