Comments
-
There are no "undo" in Jira, you'll need to add a new line
-
>directly saving a copy of my queries in centrally located place They already are. All filters in Jira are saved in, well, Jira. If you look at "manage filters", you are looking at the list of all saved filters in the system (although ones that are not visible to you are hidden)
-
There are no standard values for a reason field, it's not a field that comes with Jira off-the-shelf. Most Jira installs track "reason we've closed this" with the resolution field. The values for a reason field should be determined by the reporting you want to do on items being closed.
-
One minor point - it's not the new issue view, the summary field is mandatory on all issues, irrespective of view or other settings.
-
What are you trying to "integrate"? Jira is not a system that has "multi page documents", so I am a bit stuck on what you are trying to do?
-
I cannot help you recover things your users chose to delete.
-
Stop trying to read the database, and use the REST API as designed
-
Is the account the system admin account that you asked for (by signing up), or another Atlassian account? If it's the system admin, then no, you can't delete it because it is needed to do the administration of your system. You can (and should) remove it from projects that it may have inadvertently been added to. As for…
-
That means the service isn't running correctly. Check the logs to see what it is doing.
-
I am guessing that by "name of an issue", you mean the "summary" - to change that, click on it, or use the "edit" button.
-
Start by defining what you want the "start" time to be - how are you recording that? "Assignee" is not a time field, it holds an account.
-
You signed up for a service. Someone has to run that service and that means they have access to it. There is no way to look after something if you have no access. All of that was covered in the agreements you made when you signed up for the service. Atlassian have not "taken over" anything. Whilst they could, they would…
-
You've found workflow properties - these are not quite the right way to do this. You need to use "conditions" in your workflow. These put rules on to transitions that say things like "only group/role X can use this transition"
-
An admin always has full access to the system, as that is what the role needs to do its job.
-
You do not. Confluence needs a database for its data storage. It will ask you whether you want to use the built-in database (only suitable for evaluations, dev and test), or a full one. I think you've moved past the question about "evaluation or long term database" - click "back" and it will ask again.
-
The new view does not include this yet. The old view has a simple toggle which should be working (if it's not, could you explain what you are seeing?), and hopefully will be added to the new view soon.
-
No, there's nothing that would do this. I suspect because there's no real use for it.
-
My guess is that your issue has a silly and useless amount of comments on it, too much to be delivered in a reasonable time.
-
JQL is not SQL (because Jira issues are not "simple" tables), joins do not make any sense. But you don't need one here. Just use "and label = label1"
-
No, if you've changed to a different account, Jira can't know that it is the same person. You'll need to use bulk-edit to change the reporter, assignee and any custom fields from the old account to the new.
-
Could you check that each team is setting the resolution when issues move into a "done" type status?
-
Please could you copy and paste the actual question into the description instead of the summary? A summary is, um, a summary - something short and snappy that humans can look at and quickly, judge if they can/want to help and easily relate to a shared problem. You have pasted your whole description into the summary, and…
-
Have a look at * Portfolio for Jira, which gives you layers above epic * Structure, which allows nesting above and below (but be aware that it can get messy if you add too many) * Big Picture, which tries to give you the reporting you want without kludging your processes * Tempo for the planning and reporting without more…
-
This is a function of your browser, not Confluence. Confluence says "yes, allow spell check", but does not do a lot itself.
-
All of the fields you have named are fields that have been added by your Jira admins, probably for some form of HR project. You will need to talk to your admins about getting them removed from your projects (They do look wrong to me as well)
-
I'm afraid there's no error attached. We only need the plain text of it, and highlight/copy/paste is a lot quicker than taking screenshots.
-
No. Confluence 3 does not work on Java 7+ I would recommend installing Oracle Java 6 on RHEL (temporarily), running up a 3.5.2 installation and moving over to that first, then upgrading it to 4.highest, then 5.highest, then 6.13.6 (latest enterprise version)
-
Ah, actually, you can now. But not yourself, you have to raise a request with Atlassian and they will change your url. Choose carefully, they will not do it regularly, it's a one-off.
-
If it's not available in the field configs, then the field is not in Jira If someone has been messing with your database, then it's not hard to make a mess like this. The database is the wrong place to be looking though.
-
One of your administrators changed the name of a status, you'll need an admin to go to the list of status and change it back.