Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Member permissions on Jira ticket specific field

Arthur Harutyunyan
Contributor
November 10, 2023

Hi Admins, 

 

I have 2 types of projects, lets call them INTERNAL and EXTERNAL. 

INTERNAL: This is a project where the internal team is communicating over the tasks and organizing the whole SDLC

EXTERNAL: This is a project where the business level discussions are stored and the cost of the task/project is stored in a special field, lets name this "Cost"

PROBLEM: Sometimes there is a need for an INTERNAL member(a developer or someone else) to participate in the discussion in EXTERNAL one. So, the idea is to have the "Cost" field hidden from that internal member, but he should be able to see the other fields.

 

Hows that possible? Any workarounds?

Thanks, 

Arthur

2 answers

0 votes
matthew_bache
January 6, 2023

@Arthas nova 
I am also trying to do what I think your question was asking: to find tickets in the fixVersion immediately preceding the most recent release. (Not the next unreleased fixVersion)
So for example, if you have:
1.1 (released), 1.2 (released), 1.3 (released), 1.4 (not released), ...
the JQL would pull tickets in 1.2


Did you find a way to do this?

0 votes
Henrique Bittencourt
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 9, 2018

Hi Arthas! 

So, about your question, unfortunately, there isn't a nextUnreleasedVersion() function to help you with.

Digging a little further on the JAC I've just found this feature request:

Allow filter by "Next Unreleased Version"

But it was marked as fixed, please take a look into this comment.

Seems like you can search using the following statement:

fixVersion = earliestUnreleasedVersion()

Also, take a look into this comment:

This function appears to use the order of the "Versions" in the list NOT the dates associated with them. Also, note the list earliestUnreleasedVersion() function expects the next list to be ordered with the old/next versions on the bottom of the list with future versions on the top. (I.E. From top to bottom: Release 6 -> 5 -> 4 -> 3 -> 2 -> 1 NOT Release 1 -> 2 -> 3 -> 4 -> 5 -> 6).

Hope this can help you out.

Best Regards.

Suggest an answer

Log in or Sign up to answer