Comments
-
Yes, I'm afraid you need to create a new project of the "next gen" type, but once you have that running, you can move all the issues in from the old project. I can't think of a reason why they would lose your existing ranking, but I have not tested it.
-
Interesting, could you check the log file for errors around the point you click logout? Have you tried clearing the browser cache yet?
-
This is a better way in the long run, I just fixated on the "hierarchy" asked for.
-
Is this user going to the portal to create requests in the second project? As they're only a customer, they should not be able to create issues or work with them in a service desk project - customers only get the portal request side of it.
-
p.s. The bit I do call "dumb" is the defaults which let all your users (except customers who belong to no groups) see all your projects. That's a pain to unpick once you've started to expand past a couple of projects!
-
A simple script should be able to iterate through your directories and create and attach files over REST. On a linux box like the one you have in your screenshot, I'd start with find . type f -exec <a script to import an item> {} \; I'd write that script so that it read the file type and chose to attach or scrape it as…
-
A Cloud download includes a sysadmin account which you should be able to log straight into with a password of sysadmin. If this has failed, then you'll need to reset it - see https://confluence.atlassian.com/doc/restore-passwords-to-recover-admin-user-rights-158390.html
-
Ok, let me jump back a step. Customers just have customer accounts, you do not add them to Jira via groups or roles and they do not consume licences. They have access to portals and requests. Agents are in Jira, and have full access to the service desk project that underlies a portal. Developers are your "ordinary" Jira…
-
You'll need to read the application log to find the details of the underlying error. But I would check you are using the right version of java first, as the wrong version is one of the things I know can cause this sort of error. Try running Confluence and check with "ps -ef" where the java it runs is, then run that java…
-
Yes, they're hashed into the licence.
-
Ok, you need to be the right sort of admin (there's three types in Jira, I can't guess what type you are from just "admin rights" and it's now an essay answer on what each can do in certain circumstances). Go to the project setup again, and look at workflows this time. Descned into it and find the workflow in use for your…
-
You can go direct from 7.1 to 7.12
-
This is not quite right. The question was about stopping people from using transitions when an issue has a certain security level. The roles and groups of a user are irrelevant here, you just need a script that looks at the security level.
-
Board -> Configuration -> Columns You drag the available status from where they are now into the columns you want them in. If you are missing status, look for the "add status" near the top right, and if you don't have that, you'll need an admin to amend your workflow to add more.
-
No, I'm afraid it's not easy. Possible, but a faff. You have to add a new project (any type other than "next gen") and then use bulk-edit to move any existing issues from the old project into the new one.
-
You would probably do this with a Behaviour, as that could hide bits of the UI, but this is completely the wrong approach, as it's complex and incomplete (people can bypass it quite easily). The best option is to add a condition to all the outgoing transitions that says "if security level = X, then do not allow…
-
I would guess you created a "next gen" project, which currently have fixed notification schemes.
-
That's attachments, not logs. But the right answer for attachments.
-
* No, it's a key based on customer and licence, not the version (because Atlassian can't reliably know what version you've got, and a licence covers a huge range of them) * Yes - see https://www.atlassian.com/software/jira/download * Yes, although it's a bit complex. You'll need to set up a new Jira, empty, install any…
-
Two options (both need you to stop Jira while you amend them) * Dirty quick option - move the logs directory to the new place, then replace the logs directory with a symbolic link to the new place. * Doing it properly - amend the log4j.properties file to point to a new place. Move all the old logs (if you want to keep…
-
That is the Jira built-in "update issue field" which was written for Jira 1 if memory serves (possibly Jira 2, it's been a long time). It is only capable of updating "system" fields - the ones built into the core of Jira. You will need to find an App that provides a similar function that can update custom fields (most Apps…
-
Indeed, the system needs something to hang more data off. An email address isn't good enough, as it doesn't define a user, tell us their permissions or display name (trust me, you don't want an email address as a display name), or any of the rest of it.
-
No. Trials are 30 days for Server, with unlimited users. You can extend up to twice, but only by contacting Atlassian. Once a trial expires, you can continue with as many users as you want, but the whole system will be read-only, until you buy a licence for the right tier of active users you want.
-
So change it so there are two issue types.
-
Start at https://www.atlassian.com/software/crowd/download and then go to https://confluence.atlassian.com/crowd/installing-crowd-24248834.html
-
>we can not set customized email notifications project wise Not directly, but you can do it. Start with the docs @Gonchik Tsymzhitov has already given to help you edit the outgoing email templates. When you've got the hang of minor changes, you can move on to something a bit more clever where you could say #if ( "ABC DEF…
-
External ID is a custom field that used to be added by Jira automatically, but has been dropped (this is because it's not needed by people who are not migrating from other systems, and that's the case for a lot more of the customers now) A lot of us find we want to add it when we do integrations with other systems, or…
-
A closed issue should appear in the current sprint, in the right hand column (i.e. the end of the process) until the sprint is ended. Once an issue is done, it won't appear in the backlog because it's done, nor on newer sprints, because it has been done and doesn't need to be in them.
-
Ok, I assumed they were projects. But, lets say ABC, DEF and GHI are request types. You can map ABC to issue-type 1, and then DEF and GHI to issue-type 2, then you use the workflow with the post-function for issue-type 1 and the other one without the function for issue-type 2.
-
You can't assign issues to groups, but there is nothing to stop you having a custom field to capture a responsible group alongside the assignee, and automation should be able to fill that in for you.