Comments
-
No, because the transitions are not logged. The change of status is logged, but it's going to be an ugly and unweildy query to report on. Look in changeitem and changegroup for the basic information.
-
Ok, the Cloud is always on very recent version, so to answer the original question, no, you can't downgrade, and worse, you have no choice to avoid "upgrades". I completely understand that the changes don't work for you. I'd like to suggest reporting them as new bugs on Cloud to Atlassian, and then, before you leave…
-
I don't understand this "next phase" thing. Can you check the plain issue view - does it have an attachments section?
-
This is the community, I'm a little confused.
-
Those settings look fine for a simple proxy (although the round-robin is irrelevant for plain JIRA Server). So I doubt it's the config. As it's not JIRA, the question becomes what is your proxy doing - is it overloaded? Broken caching? Intermittent slow downs suggest load, but it's hard to tell.
-
See https://community.atlassian.com/t5/JIRA-questions/Projects-and-its-Screens-Workflows-Issue-Types/qaq-p/603467
-
I think the answer you're looking for is "same licence". JIRA Software is an application which runs on top of a JIRA Core system. A JIRA Software licence gives the user access to JIRA Software and Core (because Software doesn't actually work without all the stuff Core provides)So, you could do something like "50 software…
-
No, it's not a field at that point, it's a convenience for coders. You'll want to find or write a field that provides a display of the parent as though it's a normal field.
-
You can't do this with JQL. JQL finds issues, it doesn't do reporting or sorting of these, it's just a simple list of matches. An issue will only appear once on a list, because that's what people expect from a search. A simple export to excel is only able to dump out the list, it can't know the reasons for each hit. But.…
-
Part of the tone was because this question was posted several times by allegedly different accounts, as though a company had taken a contract to support JIRA without knowing what they were doing, and had got in loads of non-experts to do an expert's job. Also, it clearly shows no effort to bother to search for any…
-
>Specific question #1: How does one create a transition screen which allows the current assignee to set the new assignee? You were very close. Don't put a custom "user picker" on the transition screen, put the assignee field on it. You will need to make sure that the person using the transition has the permission to assign…
-
I don't understand "we cannot see in the next transition". Can you check the plain issue view - does it have an attachments section?
-
It can read its own backups. The xml exports of issues are simply not designed for transfers, that's what the xml backups are for.
-
An xml backup is useful for importing into other JIRA systems. The issue xml exports are useful for machine representations of issues, more for other non-JIRA systems to read. Although since about JIRA 5, the REST interface is generally the better way to get other systems to interact with JIRA, rather than exports.
-
Ok, that usually points to a broken add-on writing junk to the index. Are there any errors thrown when action 7 is run on the list before?
-
Ok, that makes me suspect you are on JIRA Cloud, where there's been several people unhappy with recent Tempo changes. Can you confirm that it's Cloud?
-
"Useless" is a bit strong, and too vague to be useful. You might want to explain the problem to see if we can help you fix it. But no, there's no downgrade options.
-
The original answer is out of date, you can now add values to some fields, rather than overwrite. If a field is not on the list of things you can bulk-edit, then the most likely reason is that it is not on the "edit" screen.
-
First, does the "filter statistic" in JIRA work ok? Apart from the axes being reversed, of course. If it does, then you'll have to explain what you mean by "chart macro is not helping" in Confluence? I can make the simple ones work by filling in the questions it asks.
-
The Service Desk can only expose fields that have been coded to support it (this is a two-way thing, the custom field needs to support Service Desk, and Service Desk needs to support the field) Database fields are missing one or both sides of this support, because they're too different to the standard Atlassian custom…
-
Your old workflow contains two steps/status which are not in the new workflow. You can't have issues on a status that their workflow does not support, so JIRA needs you to tell it what to change the status to in the new workflow. Note that it is listing all the questions it *might* need to ask, which is quite annoying.…
-
Yes, I'm afraid you have to change the workflow scheme for every affected project.
-
Remove the "time tracking" field from the screens the customers are using.
-
Deleting steps can't be done in a draft workflow. You will need to * Rename the current workflow * Copy the current workflow to a new one * Delete the steps, and make the other changes you need in the copy, including giving it the right name * Copy the current workflow schemes that use the current workflow * Edit the…
-
A post-function could be constructed to do something, although it might look a little odd to the user. You'll need an add-on such as automation or ScriptRunner to do this, but a post-function could * Be placed on the in-progress -> done transition for sub-tasks * Read the parent to look for other sub-tasks (and any other…
-
That doesn't sound right. I suspect you may have chosen "edit" instead of "transition issues". Status is not a field, so you can't edit it, you have to move the issues through the workflow.
-
It's anything that might cause structural change to the index, so pretty much what Błażej just said. The index is almost purely about issue data, and most of that is field based, so the general theme is "messing with fields can cause it" It is a little over-enthusiastic - a lot of add-ons don't really need it doing after…
-
JQL finds issues, it doesn't report on them. The data you're looking for is buried in the issue history. You can look at it in there, but you can't really report on it en-masse without reporting add-ons.
-
Ah, Cloud is always on the latest version, so it's definitely gone.
-
Very much so! Thank you! The short answer is simple - JIRA hides custom fields if they have no data in them. There isn't a way to change this without some coding I'm afraid.