Comments
-
I'm guessing you're using OnDemand? In which case, no. See https://confluence.atlassian.com/display/AOD/Atlassian+OnDemand+Plugin+Policy
-
Yes, you've got the right field. It's not as simple as "just an algorithm", you need a bit of background to understand what it's doing. I've bookmarked https://confluence.atlassian.com/display/AGILEKB/Troubleshooting+New+Ranking+System+Issues as it gives the right level of detail to get you started. However, it doesn't…
-
I'd read the prices page - https://www.atlassian.com/software/jira/pricing
-
For OnDemand, you don't need to "upgrade" - that's for downloaded versions. You need to increase the number of users in your OnDemand instance by requesting more from your OnDemand account.
-
No, that would defeat the point of watching and notifications.
-
Benchmarking usually means looking at performance metrics, but those could be anything from end-user speed of response through to how much time your users spend on the tool.If it helps, the story I've heard was that JIRA was written because Bugzilla was getting in the way of developers doing real work, and it's grown from…
-
Benchmarking what? If you want other issue tracking systems, have a look at http://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems - the comparison is handy and it's a pretty good long list
-
What are you trying to achieve here? Free text is free text, you can put anything into it that you want, and include delimiters if you want, but they won't actually do anything other than be part of the text. What behaviour are you looking for here?
-
There's no confusion, you're trying to change email addresses on user accounts. It's not advisable to do it with SQL, but you can do it. I don't know why you keep asking about it, or why you've suddenly started looking at the login ids when you're only interested in email. Secondly, you specifically asked about custom…
-
You already have the answer to that.
-
They're for handling external systems which allow for mixed case alongside ones that do not. Do not touch those fields, you don't need to.
-
You have already been told the answer to that.
-
Nope, because you haven't really told me what data you think you want from the custom fields, so I'm guessing. And a filter is a far better, safer way to do it. SQL is a last resort and a terrible idea. The SQL for the user changes is "update cwd_user with your changes". Remember to take a full backup before you run it,…
-
Please avoid using the database, it's complex, messy and if you get it wrong, you can destroy your installation, and you will not technically be supported if anything goes wrong. A far better option on the first one is really simple. Run and save a filter for "custom-field is not empty". Use that filter in a "filter…
-
I'm afraid that does not make sense. Are you trying to remove a user or re-activate one who was deleted?
-
Sadly, it's not available yet.
-
I don't think it will happen like this. REST respects all the settings in the application, and will probably continue to do so. The closest I think you'll get is a "bulk edit via REST" function, with the "do not email people on bulk edit" option
-
You'll need to find or write a plugin to do this for you (you could use the "script plugin" to provide most of the framework for you).
-
As per answer - edit the workflow.
-
For bulk-edit, you need to check that you've got the global permission to use it first. Then you run a filter for "issues with the wrong resolution" (e.g. status = reopened and resolution = resolved). To the top right of the issue navigator, you 'll have "bulk edit" as an option, and you can follow that through to change…
-
You don't need to edit the workflow to view what it is doing. I use the default workflow as an example because it has some very useful concepts in it. More importantly, because we can't edit it, I can rely on what you see as being the same as what I've got in front of me. You need to look at your workflow and edit that, so…
-
Simplify what you are looking at. As I said already, the strikeout is based entirely on the resolution field. Ignore everything except the resolution field. It's set (or not) by either post-functions OR if a transition goes through a screen with the field on it. That's it. Ignore the rest. Comments, status, index, forget…
-
Change the resolution to none. The strikeout indicates that the issue is "resolved", which means a resolution is not blank (doesn't matter what resolution - the decision is "set to something" versus "none"). To get into the situation you are in, I'd guess that you have edited your workflow and not realised that you need to…
-
What are the queries you are running?
-
You won't be able to do that on Cloud, it's a complex requirement that effectively needs code which you can't add to Cloud. If you were on Server, I'd use the script-runner to get a list of links of that type, check the other ends of the links and trigger the relevant transitions on the target issues.
-
You've already asked this and had it answered. https://answers.atlassian.com/questions/224061/regarding-add-the-component
-
Hmm, that does sound like an upgrade, I think I saw a comment or issue along the lines of "make admin links more direct" and this would be the sort of change I'd expect for it. At least you've found it!
-
Um, project administration is one thing, system admin is another. Which are you talking about? And could OnDemand have been upgraded and moved/removed it?
-
You've had your access rights changed. You need to talk to your other Jira admins and get them to give you your access back!
-
You can do it with other web servers, and it is possible with just Tomcat (but I don't recommend that, as it's a bit of a fiddle - certainly a *lot* more complex than just sticking Apache or Nginx in front of it)