Comments
-
That's ugly. You'll need a load of code to import a view of the old JIRA. I'd export the old issues, import them into the new JIRA and make the projects read-only on the old one.
-
It's not a problem for most Cloud users, but it would be nice to have.
-
No, Cloud does not (yet) let you define a custom domain.
-
Ok, that's the view of a single issue, in Word format. Whilst the velocity context for that contains the current issue and then some information on the sub-tasks of the current issue, I don't think it contains each sub-task. You'll need to get a handle on each and every subtask and pull that, which may require some…
-
Could you explain where you're trying to do this? It matters because the velocity context is different depending on where you are, and may not contain enough to generate what you're looking for.
-
Atlassian have a big backlog of requests. I think everyone probably disagrees with their priorities, but we wouldn't be able to agree on a "better" list ;-) I'm not sure why the proposed plugins haven't been updated - it may be worth asking the authors. Or possibly downloading the source and seeing if it can be recompiled…
-
Nope, see https://jira.atlassian.com/browse/JRA-1991 for the request and progress, along with suggestions for workarounds.
-
With an account with admin rights for the project, click "edit" on the project header screen.
-
Logs are usually in the log directory in confluence-home, assuming you've not relocated them. Check the system-information page for where that might be on your system.
-
That one catches loads of people ;-) Go to Admin -> users -> User preferences That's where the defaults are taken from (for people who have never customised their profiles. If someone has, then their profile has branched from the default and won't be updated)
-
Have you got "email me on my own changes" enabled in your profile? If it's off, then you won't get any mail from your own actions.
-
@ mentions are for mentioning people. I don't see much use for mentioning project components and what would you actually do with the mention? Think of it this way - in a car-related project, you say "@bob fixed something to do with an @tyre". Bob gets notified that someone has mentioned him, you can click on his profile,…
-
Could you explain "I need to include the project componet details like browsing a user in edit page" in more detail? I don't understand what the goal is here?
-
Yup, it is definitely not a solution I'd call "graceful" (Scraping a system to index it elsewhere when it's already got an index is never "graceful" IMHO)I'd raise the JQL function as a JIRA improvement over at https://jira.atlassian.com/browse/JRA (check to see if it's not already been raised if you can). If Atlassian…
-
Ah, I see. But it's not doing what you suggest. The addon scrapes data out of JIRA and then allows you to run queries on that. It does not add a JQL function.Doing that is the only approach I think you can do with a Connect addon. You certainly can do "Issue in hasLink(blocks)" with that method - scrape the issue for its…
-
Nope, Connect does not allow you to create JQL functions (yet). You can only do them in type-2 addons, which you cannot add to Cloud.
-
The issue security functions have worked the same way from JIRA 3 to the very latest. As you've checked that you have the permissions, and you're a member of one of the levels, my best guess is that the "security level" field is not on the create/edit screen.
-
A JIRA system administrator has all the same powers as a JIRA administrator. Sometimes it's easier to say "A JIRA administrator has a cut-down sub-set of the powers of a System admin" Your administration rights are separate from your rights as a user. An admin can always get to the admin section of a project (and hence…
-
Doesn't matter which way round it's done. The libraries in Tomcat, although required to run Jira, are not needed for building the WAR. My main client builds their Tomcat and WARs completely independently of each other - completely separate servers doing the build work!
-
(unless someone else has written a similar plugin that's demonstrably reliable)
-
I'm afraid you can't do that. Jira only has Issue and sub-task levels. You can have many types of sub-task, but that's it, just two layers.There is an open issue for "sub tasks should be able to contain their own sub-tasks", but it's not seen a lot of movement over the years, and there are a number of hideous bodges talked…
-
How are you telling JIRA that an issue at the same level as the Story is a related task?
-
In Jira-speak: A Scrum board is a view of a set of issues that are in progress, arranged in a grid style with columns for position in the process, plus options to help you rank and plan blocks of time to work on stuff A Kanban board is similar to Scrum, but doesn't plan, stuff comes in, you move it across the board as work…
-
Not without rewriting parts of the application. This isn't gospel, it's based on one of the developers here spending a day looking into it and coming back with a strong recommendation that we change the database (we took the opportunity to drop MS-SQL and move to PostGreSQL). I'd raise it with Atlassian directly for an…
-
Ooh, now that tickles a memory - having the same plugin work differently in different systems doesn't happen often, but it can. I've seen it with something I wrote once - worked fine on all the decent operating systems, but failed when on Windows! Worth looking at the differences between the systems, obviously, but I'd…
-
Sounds like a display problem in the plugin, rather than a field or indexing error. Have you checked that the version of the plugin is good for your version of Jira? Any upgrades available?
-
How are you generating the traffic-light status? It's not something Jira does natively (unless you're describing something I haven't quite recognised). Could you explain which plugin it is, or give a bit more detail if it's not a plugin?
-
Hitting return too quickly? ;-)
-
I'm a bit confused - your question is mostly about field configurations, but you start talking about screens in the middle. Screens and field configs are (effectively) totally separate things, and amending a screen has no effect on field configs at any time. Could you explain exactly what you are changing that seems to be…
-
As Joe says, downgrading is pretty much "restore a backup from before you upgraded". You could try to work out how to downgrade using SQL, but I really wouldn't recommend it. It might be more useful to simply ask why you can't use 6.2.4?