number filed with unique values

[Mohamed Saad Taha]

Dears,

I want to create number filed but this filed is accepting unique values only and can't be duplicated in any other request.

Dev team want priorities request according to numbers and this priority number cann't be duplicated in any oher request

[Dick]

Hi Mohamed,
In addition to my "solution" you could let: 

• The Creator enter a value in one of the priority slots (thus giving a ticket a priority)
• The Agent is allowed to move a slot value (= ticket name) to a new, empty priority slot (checked by a lookup items list that needs to have zero entries), thus effectively changing the priority of the ticket.

Reasoning for the above:

It is easier to deal with a full/empty fixed slot than needing to check the numbers given to random issues in the project.

Would this expanded line of thought help you?

Dick 

By voting for helpful posts and marking answers to your question, you're helping people with similar questions find a solution more quickly. Sharing is caring applies to knowledge as well :)

[Dick]

Hi @Mohamed Saad Taha , 

I'm sorry I've missed your question yesterday. Could you help me provide you an answer by telling me more about what your Dev team requires of you?

One of the unique values you can use right out of the box is the key of the Jira-issue. Maybe we can use that to come to a solution. 

Do come with some more information though, it makes solving your problem so much easier.

Regards,

Dick

By voting for helpful posts and marking answers to your question, you're helping people with similar questions find a solution more quickly. Sharing is caring applies to knowledge as well :)

[Mohamed Saad Taha]

@Dick ,

NO, Dev team want to arrange their qeueu according the filed entered by digital team for example. so if digital team entered in the prioirty number 1 to this is important and Dev team need to work on this request and digital team cann't enter number 1 again till dev team close this request and if they want to change their prioirty they have to free this number first then create new request wth this number

[Dick]

Ah, if I understand correctly, you want to create some priority slots that each can "hold" a single ticket. That ticket needs to be resolved prior to having another ticket assigned to that priority slot ?

Please confirm my assumption or correct me if I'm mistaken. 

[Mohamed Saad Taha]

Yes, exactly 

[Dick]

One solution would be to create the slots as custom fields that can hold a string. When a slot is in use by a ticket, it would be filled with the issue key of the Jira-item that is worked on.

Name:  Priority 1 slot     Value:   PROJECT-33

You could write an on-value-change triggered automation on field Priority 1 slot. 

You can access previous value from triggerissue.Priority 1 slot.fromstring, so it would be possible to check if that issue is "done". 

If it isn't, you would revert the value to the original ticket, if the fromstring is empty, or if the ticket is done, you would allow the new value (by doing nothing to the suggested change other than checking if it's the key of a valid Jira-issue).

Would this line of thought help you?

Dick

By voting for helpful posts and marking answers to your question, you're helping people with similar questions find a solution more quickly. Sharing is caring applies to knowledge as well :)

[Mohamed Saad Taha]

@Dick thanks a lot for you participation but this is not what I want I want to create new filed called DEV priority and it accept number only and can be filled by the creator and the agent can change this value to another value but it must be unique so the agent can't enter number 1 for example unless he free this number if it is used in another request