Comments
-
This is not going to happen - every field is separate, they do not share their option lists. Your choices are * Maintain four separate fields, as designed * Write a new custom field type that understands it gets its list of options from one place, but can be used in several fields * Write some automated hack that…
-
No, the upgrade process in the software will convert all the data from 4.3.6 to 5.7 for you.
-
Common transitions are NOT copies - they are reusing the same thing over again. It's a subtle distinction, but an important one. A common transition will appear >1 in a workflow, but editing, from any of the places it appears will affect all it's uses because there's only one thing. A copied transition would be a separate…
-
What do you mean by "updates"?
-
Add "order by" clauses to the end of the JQL that is behind the board. E.g. if it currently says "project X", then try "project X order by field Y"
-
* Yes, as long as they have different names * Yes, and you could put in more than one sort clause * Not directly. You could add conditions to a workflow to stop people doing it. Or find/write a listener that could intercept "field has changed" and then trigger a workflow transtion.
-
Not on Cloud I'm afraid. You'd need to write a new project template add-on, but you can't install them on Cloud. Best I can do is that I think (but have not tried) Scriptrunner can create new issues in a postfunction, so you could write one that did that, with code that says "if issue key is not <project>-1, exit", then…
-
Which email add-on? Most add-ons are provided via the marketplace, which feeds into the "universal plugin manager" in your JIRA - have a look at the admin functions for "manage add-ons" and install stuff from there.
-
This is not something I would recommend doing. You'll have to maintain it on all upgrades, and the code might not be as simple as you think.As for where to do it, I would start with a *test* system. You'll need to find the right files (I've done similar things in old versions of JIRA, but the files have changed since I…
-
You'd need to hack the core code to change the layouts, as JIRA only supports a single column layout There are requests for different layouts, but they've not been implemented yet
-
There isn't one, and I guess there never will be. Script runner is immensely powerful, but it exposes the core functions in Jira, and hence allows you to make an appalling mess if you don't know what you are doing. If I were running hosted services, I would not let people have that level of access until I trusted them, and…
-
No, there's no "easy" solution. There's a nice long discussion which covers all the stuff I can ramble about on this subject at https://jira.atlassian.com/browse/JRA-6146# I forgot - the bottom of that issue page has links to two plugins that may help
-
Yes, you're missing the way Jira works. The "field is mandatory" flag has nothing to do with screens. If a field is mandatory, you must fill it in. So it has to be on the create screen, because your users need to fill it in. That's it. To make fields mandatory later in the lifecycle of the issues, you use validators on the…
-
Two things if you want to use the home machine to run it:1. You need a static ip address, so that you can always find "home" from the internet. Or use a dynamic one which changes, plus a service like "no-ip", which will give you a fixed domain and keep in touch with your router so that when your ISP changes your IP…
-
Yes, the problems I've had with shared hosting providers are all down to what they allow you to do - often it's restricted in many of the areas you actually need. The hosts are not really for running proper applications at all. If you're going to use a hosting company, you really need one who provides you with a server and…
-
You can use any version released before the end of your license period. If your licence ends on the 10th September, and Atlassian releases 5.3.2 on the 11th, you can use anything up to 5.3.1
-
Ok, that was one thing that can break it, but you've got the right settings there. I think this needs to go to https://support.atlassian.com as a full support request, as I'd want them to check that the docs are valid and what's actually happening in your Cloud server to cause the problem. Give them the precise url you are…
-
Have you included the tempmax parameter in the url?
-
Are you using OnDemand? You cannot install addons into OnDemand (you can install some, but via your OnDemand management account, not in Confluence, and the list is strictly limited)
-
The most likely reasons: 1. You do not have "edit" permission, granted in the permission scheme for the project 2. The issue is closed - there's a flag on stauts that blocks "edit" if it is set. By default, it's set on the Closed status.
-
Ok, so when you're setting this up, you need to look at why you can't create the admin user. If it's a new clean JIRA, then this shouldn't go wrong unless the database is preventing insert/create etc, so that would tell us that your database is set up incorrectly (not the connection to it, but the database) or has a fault.
-
Have you tried what Chris and I suggested?
-
It looks like there's something wrong with your database as well as an only partial setup. It might be that a dodgy database setup is breaking the installation, but you should be seeing lots of errors in the application logs if that is the case. If JIRA can't create users during the installation, then there's something a…
-
Use the transition from deferred status back to the open status. You probably want to take a look at your workflow to see if there is such a transition and if not, what route you have to take to get there.
-
Is it just the "invite user" function? Or other admin stuff too? Could you check what groups you are in by looking at your user profile?
-
If you're using OnDemand, you have a limited range of admin rights - is that what you mean? Or is it all the admin functions? If it's all of them, could you check what groups you are in by looking at your user profile?
-
I'd write a scripted field to do that (you'd need the Script Runner add-on to do it my way, but there are some others that might do it). It could extract the data from the history and work out the hours.
-
(Sorry, hit comment too early)In other words, are your users logging into one service, or many different ones?
-
I'm sorry, that contradicts itself - you want two JIRA servers, but you want the same database? That means one JIRA.Could you explain it in terms of "services" instead? Without talking about servers or databases, explain how many Jira services you want to end up with.
-
There were a couple of attempts at clustering by third parties in the past, but they really didn't work in any useful way. I saw one of them work for a very specific situation, but it couldn't be upgraded or handle certain types of addons.I think the main question is "what are you trying to achieve", rather than the "how"…