Comments
-
You say "we have binded with local url to exter url to access globally" Does that mean all users use the same url no matter where they are? Everyone internally and externally goes to the base-url of your Confluence on something like https://yourcompany.com/confluence ?
-
Have a look at https://www.adaptavist.com/doco/display/KT/Importing+Test+Cases+from+Microsoft+Excel
-
There's three most common problems that cause this: * The name resolution - your server is unable to resolve smpt.gnet.tn to the actual server address. Try nslookup on your server to see if it gets an address and that it's the right one * A firewall blocking the route between your JIRA server and the mail server * No smtp…
-
Assuming project scope is a custom field, use admin -> custom fields to find the "configure" option for the field and add the new options in there.
-
Sorry, missed the email earlier. Yes, have a look through https://scriptrunner.adaptavist.com/latest/bitbucket/rest-endpoints.html
-
>I may not always want this field to be mandatory. You can use different field configurations for different project/issue types. Making the field optional requires you to have a placeholder for "not answered" - JIRA displays this as "none" (and removes it from mandatory fields that have a default because you don't need it)
-
You need a bit of code to do this, but there are several add-ons in the marketplace that provide the functions you need already. Set up transtions that move the issue to the previous status. Then protect them with "conditions" that "check previous status of issue" (those conditions are the things that you'll need…
-
Admin -> General settings
-
You can rename custom fields in Admin -> Custom fields. You can break filters if you do that, so warn your users if you're going to change field names.
-
No, it is not. Tarun is right - there is a single workflow for any issue type in a project.I suspect you are asking about something slightly different though, could you explain what you are looking for?
-
Jira does not give out numbers as you describe (becaue it's redundent and pointless). If you are talking about helpdesk calls, then the number is useless because you should be looking at the next one that might breach the SLA. If you're looking at a development "queue", then you should be ranking after grooming, not…
-
Yes, I'm afraid you will need a bit of code to do that. ScriptRunner is a natural choice for me, but that's because I can throw questions at Jamie's team when I get stuck.
-
My instinct would be to set up a fake domain on your network, so that when the users click on a link going to Atlassian, they land on a simple web-page saying "You're not allowed to visit Atlassian, so here's some internal stuff instead". You could embed a coupe of lines of "redirect" in javascript perfectly easily too.
-
You don't need it - it's built into Confluence now.
-
Boards don't just change from one type to another. It's not just that there's nothing in the GUI for it, there's no code either! So yes, I suspect the same names, or someone has created a new board based on your project and your quick-link to it in the project sidebar has been updated. (Your board has not changed, just the…
-
Yes, the links are fine, it's the creation part you don't get.
-
Perfect, yes, those are the windows defaults. You have a copy of everything :-) So, yes, uninstall and re-install is the next step.
-
When you say "atlassian folder" - do you mean the installation of JIRA and the data? They are separate directories (albeit you might have them under /somewhere/atlassian)
-
Workflow changes won't affect boards, unless the boards are based on filters that include status. If, for example, you had a board that said "Project in X, Y, Z and status in (open, dev, test, done)". Let's say it currently shows only issues in X and Z because project Y is not using any of those status. But then the…
-
g+d goes to the dashboards, not the project stuff. Dashboards do not belong to projects, they belong to people, and they are independent of projects ( a dashboard can be reporting on data from many projects).
-
Not that I know of. I'd use a webhook to try to poke data across, but there might be an add-on in the marketplace too.
-
I don't think you'll ever find issues that match the "definition of done" appearing in the backlog. The backlog is only supposed to show things that need doing. You should still be able to find them of course - start with a filter for "updated > date/time just before you dragged them over", and filter for anything else you…
-
What does the board filter say? Can you go to visit one of the issues directly, in standard JIRA issue view? Most important though - what status does the right-hand column in your board contain? I am guessing it is "closed", so Closed issues shouldn't appear in the backlog.
-
They have nearly everything, it depends a bit on the config. If you are using external user management (LDAP, Crowd etc), then those backups will only contain bits of the user data - you will want to reconnect the external directory after restoring. But the backups will contain the directory connection settings, so it…
-
Yes, a clean install will drop all the data. But, I assume you've got backups, so you could do a clean install and then import your data? Have a look in <jira-data>/exports - if you have not disabled the regular backups, then you can take the latest export in there and import it after you've built a clean ssytem.
-
It's usually in <jira install>work/Catalina/localhost To clear it, you should delete all the files in there. Make sure you do NOT delete the directory though, that will make it fall over again.
-
It's something one of your administrators has added (possibly a field related to a test add-on). You'll need to ask your team what they added it for, and how you should use it.
-
No, you need to be in edit mode to edit content. There are a couple of table add-ons which pop their own edits independently of the page - take a look in the marketplace.
-
Ok, that's fine, we'll have to agree to differ. But you now see that you can't reliably answer the question by using a path scheme, unless you inject extra information that might simply not be available. Confluence doesn't do it, and probably never will, because it's not as useful as a unique name system.
-
That error usually means that a file (specifically a class file) is corrupted. You may have more than one. You could try things like attaching debuggers to the Tomcat to trace down which one, but I've only really got two fixes for corrupted class files are: 1. Stop JIRA, clear the Tomcat cache, and restart 2. Re-install it