Can you explain what those views are?

Do you mean shareable dashboards?

I'm administrator in project A, additionally developer in project A, and user in project B.

For project A I need to report monthly to customer about open issues and their states. so i configure the navigator showing only the fields id, type, summary, state. then i export this view to excel.

As developer in project A I need to see additionally fields like security level, dates, reporter, environment and so on.

As user in project B I only want to see id, type, summary, state, result, assignee.

I want to configure a "view" for project A administrators, containing all required fields, another for project A developers, another for project B and so on. these "views" should be accessible from issue navigators header. it would be very comfortable, if "views" were sharable.

perhaps term "perspective" is more applicable.

I put two picture attachment which should give an impression of the wished feature.

I understand that - one of the features I also want. I can't promise when we will get it done - but its one of my pet peeves also.

Cheers,
Scott

I think to some degree, yes. But each Navigator View can only have one template, so you would have to hard code which user gets what view in the template, using e.g. group membership of the users.

Cheers,
Anton

The best place to get answers for how to customise JIRA is on the JIRA Dev forum:
http://forums.atlassian.com/forum.jspa?forumID=100

I am still not 100% sure about what you are trying to achieve. Are you trying to make different Navigator Views (e.g. Excel, Printable, Word) appear only for some projects? Or are you trying to e.g. export different columns to excel for different projects?

Cheers,
Anton

For Project 1, in the issue navigator, I want to show these field columns:

Document Name || Revision Date || Language

For project 2, and all other projects I am happy to show the default issue navigator:

Key || Summary || Assignee || Reporter || etc...

I am using one of the projects to store documents, so the overview page needs to show different fields to standard projects.

The Enterprise edition of JIRA allows to save the column that will be shown for a saved Search request:
http://www.atlassian.com/software/jira/docs/latest/issue_filters.html#filter_navigator_columns

does this feature help?

Changing the columns that are shown by default for the normal Issue Navigator resulsts, (i.e. not the Issue Navigator views) is more complicated that simply editing velocity templates. I think you will need to edit the actual source code.

Please let us know if the above feature helps instead.

Cheers,
Anton

i have added my puny vote for this, although the hint that saved filters support a custom column set and order (hereafter referred to as view) already helped:

to sum up my idea on this:
rather than attaching a given view to a saved filter it is desirable to just be able to define diff. views which are then selectable via drop down. Microsoft outlook has done it that way and is more convenient to use then having to go to another page from the navigator page or open a pop-up.

MOTIVATION:
with the current impl. u have to define the view 4 each saved filter, which is not so handy if u have several projects at a time and where u also have diff. roles in these projects

also: the information i need to be displayed depends on what i currently want to accomplish and these use cases are shared across projects and thus saved filters.

EXTENSIONS

• it should be possible to define a default view per project
• limit a view to one ore more projects (good/neede in case of custom project fields)

EXTENSION 2
separate the the sort order from the views and make these independently selectable
use case:
the sort order of issues is closely related to my use cases (ie. why i watch some issues) while the column set is fixed and hence would be nice to be selectable independently. this however might be tricky as u need depend the contents of the sort order drop down by on the column set, such that u cant select an order that needs columns currently not present. on the other hand: not present cols could just be ignored.

https://support.atlassian.com/browse/JSP-22449

Regards

Pat