Comments
-
That suggests your permissions to see them have been removed (test this by visiting a page in one of the spaces manually - if that works ok, it's not the permissions) OR that the index is broken, OR that someone has installed a hack or an add-on that hides it. You'll need to talk to your admins about all of these
-
No, because it's a new project, and JIRA doesn't have a "copy project" function, as new projects are not expected to be copies of old ones. You are going to have to come up with some work-around like a script that will duplicate the issues. Or an export/import, although I can see you're struggling with that. What I would…
-
This would need to do something similar to what was asked earlier about detecting clones in a listener - https://community.atlassian.com/t5/Atlassian-Marketplace-questions/How-to-detect-via-script-listener-if-an-Issue-was-cloned/qaq-p/460724 Most of the answer is the same, except that you won't have an issue history to…
-
There are no logs attached or pasted?
-
You'll need to start by reading the application log to see what it is doing while trying to create the project.
-
How are you implementing the tabs?
-
Yes, you add a "subtasks not closed" condition to the transition(s) leading into "done" status in the workflow. This is a function built into standard JIRA, and it can check any status, it's not just limited to "sub tasks are done"
-
You will need some code to do that. Either a custom field type that can support it, or injected javascript. The Behaviours module in the script runner add-on can do this too, it does the javascript for you.
-
The problem with a shared account is obvious - you won't know who the agent is or who is handling what. It can work in a small tight-knit team where numbers about who is doing what do not matter to the business and your agents work well together and know who is doing what, but you'll find it falls apart if your team is not…
-
No, it's generally not possible. The data "issue type created" simply is not stored as a rule. If you had the administrator audit logging enabled at the time of creation, then that does store date/time and user of new, updated and deleted issue types. But it doesn't store it permanently, and it is not retrospective -…
-
It's generally a good idea to develop on a local system, then when you've got your scripts right, promote them over to your test and live server. The basic installations listed in the article are all to go on the machine on which you are going to be doing the development.
-
Look at the error message you showed in your original before you changed the question - the error was saying that the calls to get the field data had returned an object, not a number. So yes, you need to convert the objects returned into numbers. (Trying to multiply objects tends not work - yes the objects you get from the…
-
The field values you are pulling back are objects, not simple numbers. You need to convert the contents to numbers before you can multiply them together (and bear in mind they might be nulls too, which you'll want to capture and handle)
-
Start at https://www.atlassian.com/university/certification I'm not sure I can say there are any "advantages" of doing it through Atlassian - their exams are the only way to do it.
-
You have not explained what "I am not able to login" means. Don't get a login prompt? Blank or garbage screen? Error message? Refusal that your credentials are right? What does the log say the system is doing (and, by the way, which product is it?)
-
Atlassian is increasingly expecting and asking individual users to use their sites, not shared accounts. The best you'll be able to do is go to the main id site (id.atlassian.com) and log out. That will force a new login on all the others.
-
That's a good definition, but it does give us another layer to talk about. Projects have a set list of defining fields - Key, summary, description, project lead, etc. Your deadline field is not one of them. There is no support for adding more fields to the project headers, the code simply isn't there. You will need to…
-
JIRA doesn't use the Apache web server, so there is no httpd version to worry about. If your organisation has chosen to run it behind Apache (which a lot of people do), that's fine, but it's up to you what version you run.
-
You could put the resolution on the "edit" screen, but you will need to remove it as soon as possible, otherwise your users wil start setting open issues to resolved, which is wrong and messy to fix. Using a transition is the only way to update a resolution safely. Even if it's a transition back to the same status.
-
JIRA doesn't do field security like that. If you can see an issue, you can see all of it. You can restrict comments one by one, but that's the only thing you can hide.
-
You can't do it in a post-function. They have no relationship with the front-end of JIRA whatsoever. They are chunks of code that run on the server as part of a transition. So, that takes you back to the issue view (i.e. not part of a transition), where you could use a web-fragment or (horrid) javascript to add such a…
-
* Not quite. All the docs say that you need to export the system. There is no "project export", you have to take everything. When you import from the file containing everything, you can select a single project to import. * It depends. CSV might be easier to import than XML, but the comment handling is ugly (one column…
-
There is nothing to stop you creating a sub-task type called "task", although you will need to rename the parent-level "task" to something else first. By default, JIRA Software has a sub-task type of "technical task" which is a way to avoid the naming clash, but you should feel free to use whatever names that work best for…
-
REST API, or the internal one?
-
You will be able to see them on the working board, but they're useless noise on the planning board, so JIRA Software does not show them. Before you ask, they're just noise in planning because it's nonsense to rank them (outside their containing issue), and planning is about ranking your issues.
-
Conditions are the way to do it, but you will probably want to code for them, or find an add-on that implements it already (or lets you code internally) A really simple block of code could be along the lines of "if issuetype = X then return true". That would allow the transition for issue type X, and hide it for the others.
-
The reason you can't do it with the macro is that there are no page numbers on a web-page. You can only work out what page numbers are going to occur when you print it to a specific format where the output sizing is well known. However, yes, the output to pdf has a known weakness in that when you use it, it still doesn't…
-
You will need to hack the code in JIRA in order to replace the project creation screen. This does beg the question "why?". Why are you trying to change the project create screen? I ask because there are several other answers we could give you for a number of cases, but we don't know what you're trying to do so we can't…
-
Ok, do you mean the list of options available to the user in field Y changes? Or that Y is automatically set because of a change in X? If it's the first case, then you can use a "cascading select" field to do that. If it's not that case, or you need more from the field, or it's definitely two separate fields, then you're…
-
I'm not sure we can tell you much other than to rewrite the macro to work with the new version.