Comments
-
No, you can't hide a space from the list (the hidden macro works on the body of the text, not the whole space) But if you remove a user's ability to see the space, then the space will not appear on the list.
-
Don't. Use the API instead, nodeassociation is one of many tables that is not remotely suitable for querying. What is the question you are trying to answer here?
-
They're two separate systems, so their data is separate. You'll need to run pairs of reports separately (and then maybe think about merging, but that's up to your process and what you want to see from them). If you're going to do this a lot, you probably want to think about some external reporting outside Jira, or…
-
Well, that's not strictly true. All the available valid transitions appear in the workflow control. However, the workflow control has been written so that it only displays the first two items, and if there are more, it puts them in a drop-down menu. If there are NO available transitions, then the control will disappear…
-
Chair? Seriously though, at a guess, you either want to use a table formatting in a text field (check the field configuration for the "renderer" and ensure it's rich text or markup of some sort), or you want a full table field - take a look at the table grid editor add on in the marketplace
-
Something has changed, it must have, for the change of behaviour.Postfunctions look ok, but I'd have a very close look at the ser "sla" next - has someone changed the user or their effective permissions in the project?
-
Ok, what are these functions, and what's the order? (I know most are standard system things, but it's worth checking)There's also the very obvious question - what changed at the time this problem started happening?
-
Gabrielle is asking you to check the issue history for clues - where exactly does the reporter get unset? Is it in the same group as all the other changes in the transition or is it shortly before or after?
-
Do you have other post-functions that might be setting the reporter to unassigned? You've not given us your script either, so we can't help you if there are any bugs in that.
-
Yes. I concentrated on the Quisapps add-on because if you have requirements around visibility, you might as well use it for "edit" as well. However, if you're happy with "if user can see issue, they can see all the fields", then we can talk about "edit" being limited by standard JIRA without add-ons. The basic principle is…
-
The first part of the question is really simple - no. A JIRA issue has a collection of fields. Who you are is irrelevant when you look at it - you see everything for the issue. (Except hidden comments) Atlassian have stated that they will not be doing "field security", mainly because it goes against the principle of…
-
That's not anormal JIRA error message, could you give us a screensot? Of the whole page after you click the TR-2 link
-
That's not what you asked AND it's not part of the main question. I can't read minds.
-
No. If a page is restricted, then the content is protected and the include macro will not display it to people who can't see the restricted page. Because it's restricted.
-
Just put an "include" macro on the target page, and point the include at the source page. Any edit to the source page will be reflected in the target.
-
You can export the issue navigator to a spreadsheet very easily, there's an export link to click at the top. But I suspect you want something else - "temporal, issues" doesn't explain enough for me to help you though.
-
If you cancel the subscription, you lose access to the system, and it will be deleted after a month. You can take a backup for yourself before you cancel
-
Correct, because the ability would be a disaster for users, there's no code to provide it.
-
You will need to amend the core code that handles the filter protection. Personally, I think your use case is wrong. If I create and save a filter, it is most likely because I think it is useful for my reasons, and there is absolutely no way I want anyone messing with it. You could easily break all sorts of things, and it…
-
I'm sorry, that was a badly phrased sentence - I mean you'd have to find or write one that can do remote storage. I don't know of any specific add-on that does that yet. Server versions of JIRA are mostly the same as Cloud though, they have the same functions, except for the different add-on types. They do lag in versions…
-
There's loads of ways to add storage to JIRA servers, but Cloud doesn't really have that flexibility. It provides the standard 25/100Gb and that's it. You might be able to do some clever stuff with a Connect add-on, but it'll be away from Atlassian Cloud.
-
The Atlassian subversion plugin really does only do the basics. It reads subversion for relevant information, indexes it locally, and then checks the index when a user looks at an issue. It's a passive pull - it issues a simple "what's changed since I last asked you" call to subversion and parses the result. If you want it…
-
Why it's not available is a simple answer - Atlassian haven't done it yet. At a glance, the JRA project used for tracking improvements and requests has over 9,000 issues open, and a lot of them have a higher priority and/or benefit.
-
The parent of a sub-task is not a field, it's a structural item displaying the parent issue. From memory, it can't be changed by CSV import - you need to "move" the issue to a different parent, not just change it. Epic is different again - for a sub-task, it's irrelevant, as a sub-task always belongs to a parent, which…
-
Same here, although it's a test system, and I was happily blaming other teams doing some unrelated testing on the network. I will have another look when they've finished. Our symptoms include clicking "upgrade" or "install" and the page just churning and appearing to do nothing, although when you refresh, the change has…
-
It's the mysql server that isn't working.
-
Error 13 is a MySql error - it means your MySQL user (as in the user running the server) is not able to write to that directory. Permissions usually, but also check for disk space and quota.
-
You'll need to write a workflow post-function that makes the calls you need. I'd actually start with Jamie's script runner ( https://studio.plugins.atlassian.com/wiki/display/GRV/Script+Runner ), as that gives you a lot of flexibility. On the return code side, I think I'd shy away from that directly because you'll end up…
-
A validator should return "true" for "passed validation" or "false" (and ideally, an exception message) if validation fails.The validator is passed the current issue object that the system is *going* to create, so the links should be available on it, but you'll need to check for both inward and outward links (and I'm not…
-
Links are not fields, they're relationships between issues, which makes it a bit harder than just flagging a field (in fact, the field you've tried to flag is ephemeral - it's populated by duplicating the link information into it when there are links, and the data you enter into it is used to create links, and then its…