Comments
-
I wouldn't bother with the server-only stuff directly - support for server is going away in 18 months, so it's a bit of a dead-end. But DC is staying (and has a lot in common with Server - they're the same software base), and definitely look at Cloud, that's where most server users are moving to.
-
Even with admin rights, you would not be able to do this. Team-managed and Company-managed projects are configured in totally different ways. Team-managed config is local to the project, company-managed projects use schemes to tell them what global objects to use.
-
Welcome to the Atlassian Community! That's fine, but you must have created an account for you to be able to post here, and you must have created an account to get named on subscriptions or licences! Are you trying to delete this account, or another one? Either way, you'll need to use the account to log into…
-
No, an issue can only be part of one Epic at a time. The best you can do is link to the second one with an appropriate link type.
-
Go into the issues and edit their "epic link" field, changing it to the Epic you want them to be moved under.
-
> What does use "create related issue" mean exactly? It means "we would want to push that over to the software project dedicated to that client,", but you would be keeping the communication with the client open with the Service Management Request, and your developers are free to work in their development project as fits…
-
There's no way to do that. Each custom field is a separate field, you will have to refer to each one individually.
-
Ok, that suggests your calculation is actually the problem. Is your status definitely called "TO DO" (the = is an exact string match), and the test issue has been through that status at least once (and moved into another status) After checking those two, the next thing is to insert log lines in there, so the log tab tells…
-
It's not changed, they added "next-gen" projects a few years back, and they're now called "team-managed projects". They work very differently from company-managed projects. But company-managed projects have not changed. They're still there, they still use schemes (workflows, permissions, shared fields and so on) as they…
-
Is the text in the JSM management wiki formatted? If so, the link may be displaying as one thing, but exposing a different (and incorrect) URL to the clicks. I'm really guilty of doing that a lot, here as well as in Jira and Confluence - https://community.atlassian.com for example
-
In a company-managed project, you can have many sib-task types, but they are not limited by their parent issue type - you can create a sub-task of any type under any base issue type.
-
Welcome to the Atlassian Community! Custom fields are also accessed by their id (and it's better to use this because your admins won't change it if they rename the field!) - try {{customfield_11200.value}} instead of {{issue.summary}} You'll need to look up the number, but it's not too bad - Admin -> Custom fields, find it…
-
Welcome to the Atlassian Community! You can't do this on Cloud (there's a code tweak you can make to Server/DC that converts the field to a single select on the front end, but it won't stop people using the REST API or apps to set multiple values) Your best bet is probably to create a single-select custom field with your…
-
Welcome to the Atlassian Community! Generally, it's not really Jira you need to harden, it's the service and networking. Broadly though: Run it on https and think carefully about where that is "terminated" - a very common setup is to have a proxy that does all the SSL stuff, and then has a plain http connection back to…
-
Sorry, I misread. JRJC is a library that helps coders write external apps that talk to Jira over the REST API. You're not using it, I misread php-Jira-rest-client (only saw the last three words). However, it's a similar answer - the error messages you are getting are defined in the php-Jira-rest-client, so you would have…
-
Welcome to the Atlassian Community! Do you have the rights to see the page BAR:Baz? That's the usual culprit of not being offered it in a macro's option list. The other one is that Confluence doesn't always index pages instantly. How long has BAR:Baz existed? If you have only just created it to use in the children macro,…
-
Welcome to the Atlassian Community! You can use permission schemes and roles to tell Jira who can and cannot see the issues inside projects. For company-managed projects, you can also set security levels on issues which can limit their visibility to a smaller audience (within the project permission scheme) If you do remove…
-
So you're taking a step back and re-organising your use of issues and sub-task into a sensible structure? Actually using projects as containers for issues that need to work the same way because they affect one team or system, and then boards to represent a team's work?
-
Welcome to the Atlassian Community! What errors are you getting in the MySQL log or startup call? Are you sure its the character set that is going wrong, or could it be something else? Is that setting in the right section of the file?
-
I think you could do it with a custom app, but I'm less familiar with front-end display stuff than the backend functions, so I am not 100% sure it is possible.
-
You've nearly got it. The step you need next is to go to the "field configuration scheme" for the project and edit that. It will show you a list of issue types, mapped to various field configurations (quite probably though, as I'd guess you have not edited this yet, it'll probably just say "default: TES"). You should add…
-
If it is a company-managed project, then yes, you can add multiple boards.
-
You have the output template set to multi-line text. Try changing it to "duration"
-
Have a look at the library script - there's a line that deactivates a user with a function call to deactivate the user. Change the call to activate instead.
-
Welcome to the Atlassian Community! You can't post here without an active account, which suggests you've already managed to re-activate it (at least this account, if you have another, it's a different question) My guess is that you really mean "I was removed from an Atlassian system" - in that case, you need to get in…
-
There is a lot missing from that, and a lot of it is probably in the wrong order. Start with a look at https://www.atlassian.com/agile/advantage , but the main thing that's missing is "get the mindset in place, at all levels" - you're on a hiding to nothing if your managers don't understand and embrace it.
-
An expired server licence will validate fine if you have not upgraded - they are perpetual. So, the next part of your problem is that you have upgraded Jira to a version that you did not have a licence for. And the remaining question is why (and how) you got a more recent licence for 10,000 users instead of a renewal of…
-
You definitely need to talk to Atlassian and your procurement team. You can't get increased numbers of people on a Server install any more, so I don't know how you've managed to get into this situation. What are the error messages you get when you apply the old 2000 user licence?
-
Atlassian's licence policy for apps has been in place for a very long time - they need to be licenced at (or above, that works) the number of users on the largest application. How many active users you actually have does not play into it. I'm a little confused by the change of licence too. You must have bought it quite a…
-
Ok, so how are you running the service, and what do the logs for the service runner saying? Also, can you check both application and the Tomcat logs? We've only seen one part of one of those so far.