Comments
-
It needs code to remove that, and you can't apply the code on Cloud. So I'm afraid you're stuck with it.
-
The usual cause of this is that you have not associated the workflow with the project and issue type you are working with. As "resolve" is not appearing to do anything, it suggests that the transition either has validators preventing the change of status, or it's set to loop back to the same status without any screen.…
-
No, and as far as I can tell, no one has written an add-on to provide such a field. The closest you can get is very close - a label field. It accepts new input values, but suggests exisiting ones when the user starts typing.
-
Possibly. For a long time, everyone complaining that "Cloud is slow" either refused to do the diagnostics they needed to do, or found out that their connection to the Atlassian data centre was failing them or that there were internal problems, or, in one case, really poorly configured JIRA systems (fielditis was that…
-
I'm guessing you are reading https://www.atlassian.com/legal/acceptable-use-policy ? You're absolutely right that running your security scans against their software on their serves breaches the AUP. But... that applies to their servers, not yours. You can do what you want with your servers, even if they're running…
-
Ok, so there is a database migration here as well. That does not really affect the answer though, as you are using the xml exports. You need to take the full export, import it into another system on the same version (but not necessarily the same database - the xml export handles that, as it is database agnostic), then…
-
Looks like it from here. But it's unfair to blame SR really, it's the person using it. It's a tool, and a powerful one, which means it can go wrong in the hands of the wrong people. A bit like letting my SO have the power drill. Yes, it can drill holes in things ranging from plastic through to steel, or be used as a fast…
-
You will need one of your admins to fix this. They should * Check the workflow for conditions that may be blocking the transitions you want to use * If you meet the conditions they find, then run the integrity checker and correct inconsistent workflow states.
-
That can be done inside JIRA far more easily than using SQL or reporting add-ons. Go to Issues -> Search. There is a simple search allowing you to define a search with drop-downs, but I prefer the advanced one where I can write "JQL". This is *not* SQL, but has some similarities. The main thing to understand about it if…
-
I'm not an Atlassian, but I can answer. You can run Server versions of the Atlassian stack anywhere you want Two caveats on that: * The hardware/VM has to be capable of doing it. For example, don't try JIRA on a Raspberry Pi 1. It does work, technically, but it's slower than me leaving a decent pub when I'm still thirsty.…
-
Don't. The JIRA database is a data store. It's about as optimised for reporting as I am optimised for a trip to Mars without a spaceship or suit.To give you a rough idea, look at a single issue. If it's a bit complex, you may have to join up to 40 tables, often in joins 4 deep, and do them repeatedly, just to get the basic…
-
That's a new one to me! So, some questions... Is it happening for everyone, or just one user? Is it consistent? If, for example, you go back to the pie chart again, are the labels the same rubbish, or do they change? Can you check the "system information" page for any settings related to location, region or language - are…
-
Yes, you can easily corrupt or destroy data. The code expects exclusive write access to the database, and if you're poking it at the same time as JIRA is writing, it can go horribly wrong. It's rare, yes, but it is possible to break entire tables. More common is that JIRA is caching (in several ways) data that you might be…
-
Depends on how you write the script. If you do it in something like ScriptRunner, the system will look after the indexing for you. So will batches of bulk edits, and scripting over REST. Because they all go through the API. I don't know what you're scripting here, but it's not indexing as it goes. I suspect you'd need a…
-
That's not what the transition tab is for. It's for reporting on the numbers of executions.
-
I've learned new things today, thank you :-)
-
Do it in batches, or script it over the REST interface, or script it in ScriptRunner or one of the other automation add-ons. (p.s. I've no idea what a lakh is, so I'm guessing it's larger than 1,000)
-
Not really. We don't know who told you, or where you found, the information about what would be in the release.
-
Get your administrators to remove the validation they have placed on the transition!
-
No, absolutely not. JIRA caches all sorts of things, and you should never, never, never alter a JIRA database when it is running. In general, you should not mess with the database even when it's not running, because it's not as simple as most people think. What you should do here is correct the values using a bulk edit. If…
-
Yep, I'm getting too, on one of the Cloud accounts I help out with. But not two of hte others. I've raised it with Atlassian support - I think you should do the same. ( Https://support.atlassian.com/contact )
-
Nope, it's fine. As long as your users understand never-ending epics (which your explanation above probably covers fine), it's not going to cause you many problems. It is what components are for really, but if they're not doing the job, then Epics should be ok. It's not ideal, there are cases where you may run into quirks…
-
Yes it does. There's 3 Management Coordinator Review to Code Development in the history, 3 in your comment and 3 recorded in the transistions tab. That is what it is supposed to do - count up the numbers.
-
Looks ok to me. It's counting up the transitions correctly I think.
-
Your script does not make a lot of sense. Translated into English, it asks "is the value in (custom field) equal to (yes or no)?" I suspect you need something more like crowdService.isUserMemberOfGroup(cfValues['some Custom Field'], "Group Name")
-
That won't work - even if you did set it up so that handler 1 is only a comment handler and ignores emails that are not comments, you can't be sure that it will get to the emails before handler 2.
-
What do you think is wrong with the transistions tab?
-
Heh. The largest number the table can store is 999,999,999,999,999,999 - you're going to run into all sorts of other problems well before you exhaust that range. It wouldn't wrap back to 1 though, the code will simply say it cannot increment the counter any more and not let you create a new issue.
-
I'd use Botron's Configuration Manager or Awnaba's Project Configurator. They both let you move config around JIRA systems, and both have tools to help you identify clashes.
-
>Also, the archived issues should be accessible to users at any time if they need with the same ID's and data. That completely obviates the point of an archive. Your best option is to simply put them in a state where they can't be updated. If you want to move them out to another server, then you'll need to find or write…